Topic Last Modified: 2010-03-09

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 - Microsoft Exchange Unified Messaging service isn't installed or running.


This alert indicates that a connectivity error occurred and an incoming call couldn't be answered by a Unified Messaging server. The Test-UMConnectivity cmdlet runs every 5 minutes on a Unified Messaging server. It tries to check for the server's availability by sending a SIP request. In situations, when the Microsoft Exchange Unified Messaging service isn't running and the cmdlet fails on two consecutive attempts, this alert is triggered. 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, see Testing Unified Messaging Server Functionality.

User Action

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

  • Start or restart the Microsoft Exchange Unified Messaging service.

  • Verify the event logs in the events viewer and look for warnings or errors raised approximately at the same time of the alert. Each warning and error must be verified as they might provide an indication on what cause of problems are being seeing by the Microsoft Exchange Unified Messaging service.

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

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.