Topic Last Modified: 2010-01-25

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:

From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.

Details

Product Name	Exchange
Product Version	14.0 (Exchange 2010)
Event ID	2104
Event Source	MSExchange ADAccess
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Active Directory Access
Rule Name	Every Active Directory server in the domain failed to respond.

Explanation

This Error event indicates that the Exchange server was unable to contact a domain controller in the local domain. DSAccess needs a local domain controller to perform topology discovery.

This event may occur when the Exchange server starts. For example, if no domain controllers respond when the Exchange server starts, the Microsoft Exchange System Attendant (MSExchangeSA) and all its dependent services won't start.

This event may also occur when the Exchange server and all required services are running. For example, if all domain controllers and global catalog servers become unreachable during ordinary operation, the MSExchangeSA and all its dependent services will stop.

Note:
When all domain controllers and global catalog servers go down, a new topology discovery becomes necessary.

This event can occur if the domain controllers in local or all domains become unreachable because of network problems.

User Action

To resolve this error, verify that at least one domain controller in the local domain in which the Exchange server resides is running and reachable from the Exchange server. Do one or more of the following:

Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.
Run the Dcdiag command-line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Windows Server TechCenter.

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.