xav1963
asked on
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 MSEXCHANGEADTOPOLOGYSERVIC
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)
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 MSEXCHANGEADTOPOLOGYSERVIC
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)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
ASKER
The ipv6 was disabled... must have done it sometime back to streamline services.... thanks....
ASKER