Topic Last Modified: 2010-01-26

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	^(1000\|2012)$
Event Source	MSExchange Monitoring POPConnectivity
Server Role	Ex14. Client Access
Rule Path	Microsoft Exchange Server/Exchange 2010/Client Access/POP3/POP Connectivity
Rule Name	A POP3 connectivity transaction failure occurred. The Client Access server wasn't found.

Explanation

The cmdlet that triggered this alert is the Test-PopConnectivity cmdlet. The Test-PopConnectivity cmdlet can be used to verify that the Microsoft Exchange POP3 service is running as expected.

The alert may be generated when the specified Client Access server was not found. This may be caused by a network connectivity issue. This may be a temporary problem. You can safely ignore this alert if it occurs occasionally.

User Action

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

Check network connectivity to the Client Access server.
Make sure that the Client Access server is running.
Make sure that the Microsoft Exchange POP3 service is running on the Client Access server.
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 to this topic.

For More Information

For more information about the Test-ImapConnectivity cmdlet, see Test-PopConnectivity.

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.