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:
- 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 |
^(1007|1008)$ |
|
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 |
An Outlook Web App connectivity (External) transaction failure occurred. The test credentials can't be used to test Outlook Web App. |
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 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 may indicate that the test mailbox was not found.
User Action
To resolve this problem, do one or more of the following:
- 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.
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.