Topic Last Modified: 2010-08-10

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager runs Exchange Management Shell cmdlets to monitor your Exchange organization. Running cmdlets triggers one or more Operations Manager alerts if a problem is detected.

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


Product Name


Product Version

14.0 (Exchange 2010)

Event ID


Event Source

MSExchange Monitoring UMConnectivity Local Voice

Server Role

Ex14. Unified Messaging

Rule Path

Microsoft Exchange Server/Exchange 2010/Unified Messaging/Availability/Service

Rule Name

UM Connectivity (Local Voice) transaction failure - Active Directory error encountered.


The cmdlet that ran to trigger this alert is Test-UMConnectivity. The Test- UMConnectivity cmdlet tests the operation of a computer that has the Unified Messaging server role installed and related connected telephony equipment. This alert indicates that the connectivity transactions on voice calls failed because required Active Directory information could not be found. This alert may occur in the following circumstances:

  • There are network connectivity issues.

  • A domain controller issue is not functioning correctly.

Information provided in the Operator Console may help you understand and resolve this alert. Specifically, it may help you do the following:

  • Determine the Unified Messaging server involved in the triggering of this alert.

  • Determine the error code associated with the logging of this alert.

For more information about how to test Unified Messaging functionality, see Testing Unified Messaging Server Functionality.

User Action

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

  • Make sure that the Exchange server that logged this event can connect to the configuration domain controller.

    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.

  • Review the Operator Console for detailed information about the cause of this alert. For more information, see the introduction section.

  • Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

For more information about the Test-UMConnectivity cmdlet, see Test-UMConnectivity.

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.