With the only Java I truly like in my hand I make my way to the home office.
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 Path Ping command-line tools to test network connectivity to local domain controllers.
Ensure you diagnose all other possible resolutions first such as network/storage/cpu/memory bottlenecks.
I took the day off as I needed some time to deal with government administration.
Some of these errors include: Log Name: Application Source: MSExchange ADAccess Date: 13/08/2012 AMEvent ID: 2114Task Category: Topology Level: Error Keywords: Classic User: N/AComputer: Exchange2010.domain.local Description: Process STORE. Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)).
Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description.There were two Active Directory Domain Controllers with the Global Catalog role in the same Active Directory site as the Exchange 2010 server with highspeed 1gbps LAN between the servers.When the issue occured Exchange 2010 would begin spitting the generic errors you receive whenever there is no Active Directory domain controller available.When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account - Error code=8007077f.The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. Administration of Active Directory does not have to be hard. With ease-of-use as well as powerful importing and bulk updating capabilities.Good thing this is a blog about IT issues because holey crap what a time eating, confusing and rather pointless mess government administration can be.