Topic Last Modified: 2010-01-27

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:

Details

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Event ID

1034

Event Source

MSExchange ActiveSync

Alert Type

Warning

Rule Path

Microsoft Exchange Server/Exchange 2010/Client Access/ActiveSync

Rule Name

The proxy request to a Client Access server has timed out. The server specified in the event description may be overloaded.

Explanation

This Warning event is logged if the Client Access server that issued a proxy request to another Client Access server times out while it waits for a response from the other Client Access server. Proxy requests occur when users use a Client Access server that is not in the same site as their mailbox. In this situation, the request is proxied to a Client Access server that is in the same site as the mailbox. This event may occur if one of the following conditions is true:

  • The Client Access server that receives the proxy request is under a heavy load.

  • The Client Access server that receives the proxy request is not operating correctly.

User Action

To resolve this warning, consider the following:

  • If this event is infrequently logged, no user action is required.

  • If this event is frequently logged, do one or more of the following:

    • Consider whether you can decrease the load on the mailbox server specified in the event description.

    • Review the Application log of the Client Access server that receives the proxy request for other events that could indicate the root cause of performance problems on that server.

    • Check network connectivity between the Client Access servers. Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, Advanced network adapter troubleshooting for Windows workstations.

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.