SBS 2008 Box - MS Exchange Transport stuck on "Starting"

For over a year I run on a little HP desktop computer the SBS 2008 (SP1) with no problems. It is the only server and DC in a small network of 5 computers and users. This morning I had to restart the server and the MS Exchange Transport is stuck on "Starting" and the Information Store is not started. When I try to start the store, it times out. I played with the service permissions and checked dependencies and nothing seems to help. No changes occurred before the restart. I do not run Forefront on it... Any help is appreciated. Here are the common errors in event viewer -

Evt ID - 2114      Source - MSExchange ADAccess
Process MAD.EXE (PID=2088). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.


Evt ID - 21102      Source - MSExchange ADAccess
Process MAD.EXE (PID=2088). All Domain Controller Servers in use are not responding:
SBS2008.xxxx.local
 

Evt ID - 2114      Source - MSExchange ADAccess
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1316). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

Evt ID - 1003      Source - MSExchange FDS
Process MSExchangeFDS.exe (PID=3904). Temporarily unable to connect to Active Directory to read configuration data for object OAB (The Exchange Topology service on server localhost did not return a suitable domain controller.). Will wait for 60 seconds and retry.  (Warning)
xav1963Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

xav1963Author Commented:
Also ran dcdiag and of course many attempts to start service... Event ID: 0xC0002720. String reads - "the application-specific permission settings do not grant local activation permission for the COM Server application with clsid". Could it be just a permission issue?
0
MorasivaCommented:
Hi,

If you uncheck the IPv6 protocol from your network interface card on your Windows SBS 2008 server you may face this kind of issues.

Make sure that IPv6 protocol from your network interface card is enabled.

http://blogs.technet.com/b/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Viral RathodConsultantCommented:
Your Exchange server is not able to communicate with Active Diectory,


1) Make sure "MS EXCHANGE AD TOPOLOGY SERVICE" is up and running fine
2) Make sure communication between AD and Exchange is working fine
2) Run DCDIAG on Domain Controller to make sure there are no errors check the AD releated service "Netlogon" is up and running fine.

In case if the above steps does not resolve the issue ,then i would suggest you to reboot both the server and check if the issues is still persist

Please letus know the results.
0
xav1963Author Commented:
The ipv6 was disabled... must have done it sometime back to streamline services.... thanks....
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.