Export (0) Print
Expand All

Exchange Control Panel connectivity (Internal) transaction failures.

 

Applies to: Operations Manager Management Pack for Exchange 2010

Topic Last Modified: 2011-08-02

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.

 

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Event ID

^(1000|1001)$

Event Source

MSExchange Monitoring ECPConnectivity Internal

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 (Internal) transaction failures.

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 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 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.

  • Log on to the Client Access server and run the Test-ECPConnectivity cmdlet 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.

If you are not already doing so, consider running the Exchange tools, which have been 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 and improve mail flow. 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.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft