Information Store will not mount in SBS 2008 following uninstall of VMWare Player
We have a new installation of SBS 2008 which has been working fine for several weeks. Someone installed VMWare Player on the server and this seems to have caused some networking problems. For instance the system would not connect to the Internet until after
the VMWare Player was uninstalled. After some troubleshooting the system seems to be working well with one exception. The information store will not mount. We are getting the following event IDs:
Application Log:
Event ID: 2114
Source: MSExchange ADAccess
Description: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1696). 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.
Event ID: 2601
Source: MSExchange ADAccess
Description: Process MSEXCHANGEADTOPOLOGY (PID=1696). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft
Exchange,CN=Services,CN=Configuration,... - Error code=80040a01.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
Event ID: 7005
Source: MSExchangeTransportLogSearch
Description: Microsoft Exchange couldn't read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service
on server localhost did not return a suitable domain controller.
at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure)
at Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts()
at Microsoft.Exchange.Data.Directory.TopologyProvider.GetConfigurationNamingContext()
at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId)
at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId)
at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator,
CreateObjectsDelegate arrayCreator)
at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor)
at Microsoft.Exchange.Data.Directory.ADSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties)
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults)
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindServerByFqdn(String serverFqdn)
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindLocalServer()
at Microsoft.Exchange.Transport.LocalServerConfiguration c__DisplayClass2. TryLoadLocalServer b__0()
at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount).
Event ID: 2102
Source: MSExchange ADAccess
Description: Process MAD.EXE (PID=1400). All Domain Controller Servers in use are not responding:
PEC-SERVER.pars.local
Event ID: 9153
Source: MSExchangeSA
Description: Microsoft Exchange System Attendant reported an error '0x80004005' when setting DS notification.
System Log:
Event ID: 7031
Source: Service Control Manager Eventlog Provider
Description:The Microsoft Exchange Transport service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Event ID: 7024
Source: Service Control Manager Eventlog Provider
Description: The Microsoft Exchange Information Store service terminated with service-specific error 0 (0x0).
Using the LDP.exe utility, I am able to open a connection to port 389, but I am unable to connect to 3289. The error code is: LDAP_SERVER_DOWN 0x51
Cannot contact the LDAP server.
Any suggestions on troubleshooting this issue are much appreciated.-- Zac Mutrux President, Sarai LLC http://sarai.org Technology guidance, management, and support. Service Desk: 415-359-3781 Mobile: 415-513-8612 Facebook: http://sar.ai/facebook LinkedIn: http://sar.ai/linkedin Twitter: http://sar.ai/twitter
February 7th, 2011 1:33pm
Actually I am able to connect to the GC using LDP.exe, I had the wrong port number. Should have been 3268.-- Zac Mutrux President, Sarai LLC http://sarai.org Technology guidance, management, and support. Service Desk: 415-359-3781 Mobile: 415-513-8612 Facebook: http://sar.ai/facebook LinkedIn: http://sar.ai/linkedin Twitter: http://sar.ai/twitter
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2011 2:15pm
Microsoft Exchange System Attendant service also will not start...-- Zac Mutrux President, Sarai LLC http://sarai.org Technology guidance, management, and support. Service Desk: 415-359-3781 Mobile: 415-513-8612 Facebook: http://sar.ai/facebook LinkedIn: http://sar.ai/linkedin Twitter: http://sar.ai/twitter
February 7th, 2011 4:41pm
Contacted Microsoft Professional Support and resolved the issue by following these steps:
Enabled IPv6 on the network adapter Ran the Connect to Internet wizard Ran the Fix my Network wizard Started the Information Store
Now all is working great, and since the resolution was so simple Microsoft didn't even charge us for the call.-- Zac Mutrux President, Sarai LLC http://sarai.org Technology guidance, management, and support. Service Desk: 415-359-3781 Mobile: 415-513-8612 Facebook: http://sar.ai/facebook LinkedIn: http://sar.ai/linkedin Twitter: http://sar.ai/twitter
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2011 5:12pm