MSExchange ADAccess 2114

In a recent project, I experienced a problem (at least by the messages on the Installation Wizard on eSales and Viewer - see image below).. This problem occurred (at least in my case) the installation of the Hub-Transport. Below is the message displayed EventViewer ...

MSEXCHANGEADTOPOLOGYSERVICE.EXE Process (PID = 1256). 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 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.

... Such an error occurs in Exchange Server 2007.2010. The resolution is put to the same Exchange server account in the Domain Admin group. After inclusion of the server group, restart the server and reinstall Exchange (if the problem has been presented in time of installation.).

Also spent a similar problem with Exchange Server 2003 ... in this case, the situation was regarding the deletion of an account of the Exchange server object AD.A restoration was carried out via ADRESTORE and even after inclusion of the restored object in the security groups required for Exchange Server Exchange services failed to initialize ....

Appears in the Event Viewer event ID 2114 MSExchange DSAccess.

In this case, I performed the following procedures:

1. After the deletion of the object, restore the same with ADRESTORE;
2. Add in the server security groups required (in some cases, these steps alone are enough to return to normal services);
3. Remove the network cable from the Exchange server;
4. Place the Exchange server in Workgroup and restart the server, without attaching the network cable;
5. In AD, reset the account of the Exchange server;
6. Plug the cable into the Exchange server and put it back in the field;
7. Restart the server;

After these procedures, the services back to work!

Another very common procedure for troubleshooting permissions on an Exchange organization, and runs the setup / domainprep command again in DC.

Hope that helps!