Topic Last Modified: 2010-03-24
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 |
^(1012|1000)$ |
Event Source |
MSExchange Monitoring ECPConnectivity External |
Server Role |
Ex14. Client Access |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Client Access/Exchange Control Panel/ECP Connectivity |
Rule Name |
Exchange Control Panel connectivity (External) transaction warnings. |
Explanation
The cmdlet that triggers this event is the Test-ECPConnectivity cmdlet. The Test-ECPConnectivity cmdlet tests Exchange Control Panel connectivity for all Microsoft Exchange Server 2010 virtual directories on a specified Client Access server for all mailboxes on servers running Exchange 2010 in the same Active Directory site. The Test-EcpConnectivity cmdlet can also be used to test the connectivity for an individual Exchange Control Panel URL.
This alert indicates that some of the transactions during the Exchange Control Panel connectivity test generated warnings.
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.
- 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 2010 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.
For More Information
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.