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	2110
Event Source	MSExchange ADAccess
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Active Directory Access
Rule Name	The Exchange Active Directory Provider couldn't bind to Active Directory.

Explanation

This Error event indicates that the Active Directory Provider cannot bind to Active Directory. This could be caused by network problems or an incorrect configuration. This is a critical error if no other domain controllers are available for load balancing.

User Action

To resolve this error, do one or more of the following:

Check the Application log for related events. The detail in other MSExchange ADAccess events and other events may help determine the root cause of this warning. Increase diagnostic logging for the MSExchange ADAccess\Topology category to Lowest or higher. For detailed information about how to increase logging, see Manage Diagnostic Logging Levels.
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 about the Get-EventLogLevel and Set-EventLogLevel diagnostic logging cmdlets, see the following topics:

get-eventloglevel
Set-EventLogLevel

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.