Exchange 2010 servers can't communicate with Active Directory

[TAREQ01]

Installed exchange2010 2 mailbox and 2 cas & hub servers over hyper v , everything worked well for 1 day .

Then EMC can not intliaze and exchange services on all servers suddenly stopped working .

Checked logs and all exchange servers they all report that they can not communicate with AD servers with the following events

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1780). Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)).

" Process STORE.EXE (PID=4692). 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. 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"

" Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96f. "

" Error 0x96f connecting to Active Directory."

Although AD servers are functioning well and all dnssettings are correct . the domain/forest functional levels is windows 2008 R2

can you please help this is my production servers and iam clueless .
Also this message on mailbox servers

 

[Neil Hobson [MVP]]

It might be worth double-checking your IP addresses, DNS settings, etc, and possibly running tools like DCDIAG and NLTEST (from the Exchange server) to confirm that there are no connectivity issues and that the server is in the correct AD site, etc.Neil Hobson, Exchange MVP

 

[jader3rd]

Last person who ran into this on this forum had to reboot their DC to get the errors to go away.

 

[Xiu Zhang]

Hi,

First please try to run DCdiag from Exchange Server to see if any error would occur.

Domain Controller Diagnostics Tool (dcdiag.exe)

http://technet.microsoft.com/en-us/library/cc776854(WS.10).aspx

Please run ExBPA to have a health scan.

Please check event 2080 to see if you have the correct dc listed there.

Event ID 2080 from MSExchangeDSAccess

http://support.microsoft.com/kb/316300

Regards,

Xiu

 

[Digby Cunningham]

For anyone elses' reference, I had a similar issue I struggled with overnight after a restart; Event ID's 2114, 2080, 2601, 2604 and more; all related to MSExchange ADAccess failure to discover topology/active directory access errors. The Exchange Servers group had the proper server in it, an the correct permissions were set in the Default Domain Controllers Group Policy for manage auditing and security logs --- something else was amiss.

Earlier this week a staff member had 'inadvertently' powered off the primary APC Battery Backup which abruptly turned off the Exchange server, and caused some database corruption I had to manually repair. This fresh in my mind, and now its not starting, I focused on that.

After pulling a lot of hair, and chain smoking far too many packs of cigarettes drilling through all the Exchange errors, it came down to something rudamentarily simple --- Antivirus.

During the restart this evening our Antivirus did a fresh install/upgrade and it wiped the Exceptions. Putting in folder exceptions for C:\Program Files\Microsoft\Exchange and D:\Exchange Server (our DB's are on a separate disk channel/array) all the Exchange services started successfully and normally.