Export (0) Print
Expand All
Expand Minimize

Outlook Web Access Test-OwaConnectivity (External) transaction failures

 

Topic Last Modified: 2009-06-15

The Exchange Server 2007 Management Pack for Operations Manager runs Exchange Management Shell cmdlets to monitor the Exchange environment. Running cmdlets triggers one or more Operations Manager alerts if a problem is detected in your Exchange environment.

 

Product Name

Exchange

Product Version

8.0 (Exchange Server 2007)

Event Source

Test-OwaConnectivity

MOM Rule Path

Microsoft Exchange Server/Exchange 2007

MOM Rule Name

Exchange 2007 Test OWA Connectivity External Monitor

The cmdlet that triggered this alert is the Test-OwaConnectivity cmdlet. The Test-OwaConnectivity cmdlet can be used to test the connectivity of all Exchange 2007 Outlook Web Access virtual directories on a computer running Exchange 2007 that has the Client Access server role installed. It can also be used to test connectivity of a single Exchange 2007 Outlook Web Access URL.

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

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 back-end Mailbox server which the transaction is using is running. You can determine the back-end server by examining the CAS Synthetic Transaction State view in the Operations console and looking at the Target column (the Source Server column indicates the Client Access server).
  • Review the Application log on the Client Access 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.
  • Ensure that the other required Exchange 2007 services are running. Review the Client Access Servers Active Alerts view to determine if there are alerts related to stopped services on the Client Access 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 about the Test-OwaConnectivity cmdlet, see Test-OwaConnectivity.

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

noteNote:
  If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you ensure that your configuration follows Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Run the tools from the Toolbox node of the Exchange Management Console. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.
 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft