Topic Last Modified: 2010-07-06

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:

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 events that have been logged that meet the criteria of this Operations Manager alert.

Details

Product Name	Exchange
Product Version	14.0 (Exchange 2010)
Event ID	^(1000\|1001)$
Event Source	MSExchange Monitoring OWAConnectivity External
Server Role	Ex14. Client Access
Rule Path	Microsoft Exchange Server/Exchange 2010/Client Access/Outlook Web Access/OWA Connectivity
Rule Name	Outlook Web App connectivity (External) transaction failures.

Explanation

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. It can also be used to test connectivity of a single Exchange 2010 Outlook Web App URL.

This alert indicates that some of the transactions during the Outlook Web Access connectivity test failed.

User Action

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

Review the details of the alert message to determine the specific error.
Make sure that the Mailbox server that the transaction is using is running. You can determine the correct backend server by examining the CAS Synthetic Transaction State view in the Operations console, and then examining the Target column. (The Source Server column indicates the CAS server.)
Review the Application log on the CAS server for related events. For example, events that occur immediately before and after this event may provide more information about the cause of this error.
Make sure that the other required Exchange 2010 services are running. Review the CAS Active Alerts view to determine whether any alerts that are related to stopped services are logged on the CAS server.
Log on to the Client Access server and run the Test-OwaConnectivity cmdlet manually.
The cmdlet runs against a back-end Mailbox server using a specific mailbox. Ensure that this mailbox has been created by running the new-TestCasConnectivityUser.ps1 script.
This transaction tests the external OWA URL, which needs to be set on each Client Access server. Ensure that the Set-OwaVirtualDirectory cmdlet has been run on the Client Access server.

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.

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.