Topic Last Modified: 2010-09-07

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager includes a performance data collection engine that is used to query performance counter objects on computers running Exchange 2010. For this Operations Manager rule, data is collected by using the performance counter specified in the Details table.

To review the value of the performance counter that generated this alert, in Operations Manager, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.

Details

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Object Name

MSExchange RpcClientAccess Per Server

Counter Name

RPC Failed Backend Connections

Sample Interval

60

Server Role

Ex14. Client Access

Critical Error Threshold

2

Rule Path

Microsoft Exchange Server/Exchange 2010/Client Access/Outlook

Rule Name

MSExchange RpcClientAccess Per Server RPC Failed Backend Connections - sustained for 5 minutes - Red (>2)

Explanation

This alert indicates that RPC connectivity between the middletier Exchange 2010 Client Access Server (CAS) and the backend mailbox server has failed for an extended period. In this scenario, you may experience one or both of the following symptoms in an Exchange organization:

  • MAPI clients such as Outlook hang, and the following notification appears on the client computers:

    Outlook is retrieving data from Microsoft Exchange Server <ServerName>

  • Devices such as BlackBerry devices drop their connections to the server or experience timeout errors when they send or receive messages. In this scenario, information that resembles the following may be logged on the Blackberry Enterprise Server (BES):

    • MAPI call failed. Error 'Network problems are preventing connection to the Microsoft Exchange Server computer.

One of the client access improvements that Microsoft Exchange Server 2010 includes is to support MAPI connections to the Client Access server role. This change required creating the Microsoft Exchange RPC Client Access service on the Client Access server.

The RPC Client Access service establishes an RPC endpoint on a Client Access server to which MAPI clients such as Microsoft Office Outlook can connect.

Note:
In earlier versions of Exchange, MAPI clients create an RPC connection to servers running the Mailbox server role.

In Exchange 2010, the Client Access servers communicate with Mailbox servers to give MAPI clients access to Exchange mailboxes. This new functionality gives Exchange 2010 the following advantages over earlier versions of Exchange:

  • It isolates the information store from direct client access.

  • It provides greater integration with the Exchange 2010 high availability strategy.

  • It provides a more reliable system in the event that an issue affects the information store.

For more information, see Understanding RPC Client Access.

If a network issue exists between a CAS server and the mailbox servers, you may experience intermittent issues when you connect MAPI clients to their mailboxes.

The RPC Failed Backend Connections counter represents the number of failed RPC connections between the middletier CAS server and the back-end mailbox server.

User Action

To resolve this error, 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.

  • Verify network connectivity between the CAS server and back-end mailbox servers.

  • Examine networking devices that are positioned between the CAS server and mailbox servers. Specifically, look for the following issues:

    • Determine whether all network devices and network adapters are functioning correctly.

    • Determine whether any network devices have an idle timeout value that is set too low. To work around an idle-timeout issue, you may want to modify the KeepAlive behavior on the CAS server or on a mailbox server. For more information, see Microsoft Knowledge Base article 314053, TCP/IP and NBT configuration parameters for Windows XP.

    • Verify that the MTU size limit that is set on any network device is not lower than the default settings in Windows.

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

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.