Topic Last Modified: 2010-07-28

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:


Product Name


Product Version

14.0 (Exchange 2010)

Event ID


Event Source

MSExchange Monitoring MAPIConnectivity

Server Role

Ex14. Mailbox

Rule Path

Microsoft Exchange Server/Exchange 2010/Mailbox/Mailbox Monitoring

Rule Name

Databases were moved while the Test-MAPIConnectivity cmdlet was running on this server.


The Test-MAPIConnectivity cmdlet triggers this Error event. The Test-MAPIConnectivity cmdlet is used to verify Microsoft Exchange functionality by logging on to a mailbox that you specify. This event indicates that the Exchange Databases were moved at the same time that the Test-MAPIConnectivity cmdlet was monitoring a mailbox.

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.

  • To review detailed information about the cause of this alert, use the Operations Console in Operations Manager. For more information, see the "Introduction" section in 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 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.

  • Make sure that the other required Microsoft Exchange Server 2010 services are running. Review the Client Access Servers (CAS) Active Alerts view to determine whether any alerts that are related to stopped services are logged on the CAS server.

For More Information

For more information about the Test-MAPIConnectivity cmdlet, see Test-MapiConnectivity.

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.