Topic Last Modified: 2010-07-11

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	500
Event Source	MSExchange Monitoring CasConnectivityTestCredentials
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Mailbox/Mailbox Monitoring
Rule Name	Error while running Set-CasConnectivityTestCredentials

Explanation

The Set-CasConnectivityTestCredentials cmdlet triggers this event. The Set-CasConnectivityTestCredentials cmdlet is used to set the credentials that are used to run server testing scripts on Client Access Server (CAS) servers. This Error event indicates that the Set-CasConnectivityTestCredentials cmdlet did not run.

User Action

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

To help repair any issues with the mailbox account that exists for your mailbox server, you can run the New-TestCasConnectivityUser.ps1 script. To do this, follow these steps:
1. Open the Exchange Management Shell.
2. Locate the Scripts folder under the installation path for Microsoft Exchange Server 2010, for example: \Program Files\Microsoft\Exchange Server\Scripts, and then run the New-TestCasConnectivityUser.ps1 script.
3. Repeat this process one time in each Active Directory site that you want to monitor.
Note:

If you have several organizational units that are named Users in your directory, you will have to specify the organizational unit in which to store the user.
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.

Note:
If you have several organizational units that are named Users in your directory, you will have to specify the organizational unit in which to store the user.

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.