The Test-OutlookConnectivity (Internal) cmdlet failed to run


Applies to: Operations Manager Management Pack for Exchange 2010

Topic Last Modified: 2013-01-22

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


Product Version

14.0 (Exchange 2010)

Event ID


Event Source

MSExchange Monitoring OutlookConnectivity Internal

Server Role

Ex14. Client Access

Rule Path

Microsoft Exchange Server/Exchange 2010/Client Access/Client Access Test Configurations

Rule Name

The Test-OutlookConnectivity (Internal) cmdlet failed to run.

The Test-OutlookConnectivity cmdlet triggers this event. The Test-OutlookConnectivity cmdlet is used to test end-to-end Microsoft Outlook client connectivity in the Microsoft Exchange Server 2010 organization. This includes testing for Outlook Anywhere (RPC/HTTP) and TCP-based connections.  This Error event indicates that the Test-OutlookConnectivity cmdlet failed to run.

To resolve this error, do one or more of the following:

  • If the Test-OutlookConnectivity cmdlet test fails, the output from the cmdlet indicates the step that failed. Use this information to help pinpoint the cause of the issue.

  • Use the Exchange Remote Connectivity Analyzer (ExRCA) to run the Outlook Anywhere connectivity test. This test provides a detailed summary that indicates the point at which the test failed, and the steps you can take to fix the issue. To run the test, go to

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

  • Use the Exchange Best Practices Analyzer (BPA) to verify the health status of the Client Access servers (CAS). For more information about the BPA, see Exchange Best Practices Analyzer.

  • Verify that the “Microsoft Exchange RPC Client Access” service is started.

  • To review detailed information about the cause of this alert, use the Operations Console in Operations Manager. For more information, see the introduction to this topic.

  • 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 other methods. 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 Product Support Services, be sure to review your organization's guidelines first.

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.