Topic Last Modified: 2010-07-05

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 OWAConnectivity External

Server Role

Ex14. Client Access

Rule Path

Microsoft Exchange Server/Exchange 2010/Client Access/Client Access Test Configurations

Rule Name

Failed to execute the Test-OWAConnectivity (External) diagnostic cmdlet.


The Test-OwaConnectivity cmdlet triggers this alert. The Test-OwaConnectivity cmdlet can be used to test the connectivity of all Microsoft Exchange Server 2010 Outlook Web App virtual directories on a computer that is running Exchange 2010 and that has the Client Access Server (CAS) server role installed. This cmdlet can also be used to test connectivity of a single Exchange 2010 Outlook Web App URL.

This alert indicates that the Test-OwaConnectivity cmdlet did not run.

User Action

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

  • Make sure that the Exchange 2010 CAS server is running.

  • Review Operations Manager for detailed information about the cause of this alert. For more information, see the "Introduction" section in this article.

  • In Event Viewer, review the Application log on your CAS server for events that may be associated with this alert. Use that information to determine the cause of the problem.

For More Information

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

For information about Outlook Web Access, see Managing Outlook Web App.