We're using Windows 2008 R2 with Exchange 2010, the server is currently a global catalog server and running exchange. We've upgraded from SBS 2003 and the old server is still running but was to be removed from the domain any day now. Everything had been working properly for about a year but today after the server was reset everything just stopped working. The application event log shows multiple errors that just continue in an endless loop every few minutes, I've googled each one individually and so far none of the suggested fixes have helped. I've reset the server multiple times without luck.
The only change that was done to exchange recently was we listed static domain controllers and global catalog servers using (Set-ExchangeServer -Identity <server_name> -StaticDomainControllers DC-01.dc.local)and (Set-ExchangeServer -Identity <server_name> -StaticGlobalCatalogs DC-01.dc.local,DC-02.dc.local)because exchange was still using the old SBS2003 server. It had been reset at least once since doing this and everything continued to work. I assume this is what's causing the issue but I have no way to undo it since I can't get exchange to start and I'm not sure why it would work properly for a few days if this is the case.
Event ID: 3176
The Microsoft Exchange Replication service attempted to start the Active Manager RPC server but failed because an error occurred when attempting to read the Exchange Servers universal security group SID from Active Directory. Error:
The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.
Event ID: 2114
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2252). 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: 1002
The Microsoft Exchange Throttling Service encountered an Active Directory error while building an RPC security descriptor. This failure may indicate that no Domain Controllers are available at this time. The service will be stopped. Failure details: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.
at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure)
at Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts()
at Microsoft.Exchange.Data.Directory.ADSession.GetConfigurationNamingContext()
at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.GetWellKnownExchangeGroupSid(Guid wkguid)
at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.GetExchangeServersUsgSid()
at Microsoft.Exchange.Data.ThrottlingService.ThrottlingRpcServerImpl.GetRpcSecurityDescriptor()
at Microsoft.Exchange.Data.ThrottlingService.ThrottlingRpcServerImpl.<>c__DisplayClass1.<TryGetRpcSecurityDescriptor>b__0()
at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation
Event ID: 1005
The Mailbox Replication service was unable to determine the list of mailbox databases hosted in the local Active Directory site.
Error: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.
Event ID: 1121
Error 0x96f connecting to Active Directory.
Event ID: 5000
Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96f.
Event ID: 2114
Process STORE.EXE (PID=8336). 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.