locked
How to monitor exchange cas server with high level of RPC faults in SCOM. RRS feed

  • Question

  • We have an Exchange server CAS experiencing a high amount of RPC faults.

    RPC fault of “The server is too busy to handle the call.

    Is there a way to monitor this in SCOM??

    Outlook clients MSRPC Faults with an error code of 0xC010014 with a description of “nca_server_too_busy – The server is too busy to handle the call.”

    We are using a F5 to load balance outlook connections and so when we removed this server and reboot it RPC faults decreased and outlook connections were successful.

    We did not see any event id's to correspond to this high RPC event.


    dsk


    • Edited by kimdav111 Wednesday, April 18, 2012 11:37 PM
    Wednesday, April 18, 2012 11:37 PM

Answers

  • What version of Exchange do you have?  You can check this via performance counters as descriped here:


    Exchange 2010: http://technet.microsoft.com/en-us/library/ff367871.aspx

    Exchange 2007: http://technet.microsoft.com/en-us/library/bb201689(v=exchg.80).aspx




    The following table shows RPC client throttling counters.

    Counter Description Threshold Troubleshooting

    MSExchangeIS Client (*)\RPC Average Latency

    RPC Average Latency is a server RPC latency, in ms, averaged for the past 1,024 packets.

    Should be less than 50 ms on average for each client.

    Wide disparities between different client types, such as IMAP4, Microsoft Outlook Anywhere, or other clients (MAPI), can help direct troubleshooting to appropriate subcomponents.

    MSExchangeIS\Client: RPCs Failed:Server Too Busy/sec

    Shows the client-reported rate of failed RPCs (since the store was started) due to the server too busy ROC error.

    Should be 0 at all times.

    Higher values may indicate RPC threads are exhausted or client throttling is occurring for clients running versions of Outlook earlier than Office Outlook 2007.

    MSExchangeIS\Client: RPCs Failed:Server Too Busy

    The client-reported a number of failed RPCs (since the store was started) due to the server too busy ROC error.

    Should be 0 at all times.


    Regards,

    Mazen Ahmed


    Saturday, April 21, 2012 7:27 AM