Topic Last Modified: 2010-07-12
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 |
^(1010|1011)$ |
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 |
There was an Outlook Web App connectivity (External) transaction failure. The Client Access server configuration check failed. |
Explanation
The Test-OwaConnectivity cmdlet triggers this alert. The Test-OwaConnectivity cmdlet is 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 indicates that an Outlook Web App transaction failed because of a misconfiguration.
User Action
To resolve this problem, do one or more of the following:
- Review the Application log and System log on your Exchange 2010
servers for related events. For example, events that occur
immediately before and after this event may provide more
information about the root cause of this error.
- Review Operations Manager for detailed information about the
cause of this problem. For more information, see the "Introduction"
section in this article.
- Resolve your issue by using self-support options, assisted
support options, and other resources. You can access these
resources from the Exchange Server Solutions Center. From this page,
click Self-Support Options in the navigation pane to use
self-help options. Self-help options include searching the
Microsoft Knowledge Base, posting a question at the Exchange Server
forums, and others. Alternatively, in the navigation pane, you can
click Assisted Support Options to contact a Microsoft
support professional. Because your organization may have a specific
procedure for directly contacting Microsoft Technical Support, be
sure to review your organization's guidelines first.
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.