none
Event ID 106 Exchange Common Errors

    Question

  • Variants of this have been asked before but our Exchange 2010 CAS/HUB servers are producing lots of Error 106 errors in the event logs:

    Performance counter updating error. Counter name is <var>xyz</var>: Foreground RPCs Failed, category name is MSExchange RpcClientAccess. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.

    There are various counters being reported. I noticed there is a KB article about this for an RPC service and it says it can be ignored but just wanted to check about the rest.

    - Will there be any functionality issues or is it purely counter/perfmon related?

    - Can they just be ignored?

    - Any fix?

    I noticed that it is often a case of the counters being for a different role to what is installed so this may well be the case?

    Monday, August 12, 2013 4:19 PM

All replies

  • Hi,

    Please see the below link to assist you with your problem.

    http://social.technet.microsoft.com/Forums/exchange/en-US/079598ef-08fe-49b6-af5f-8920d8b34a39/msexchange-common-error

    Monday, August 12, 2013 11:20 PM
  • Thanks but it doesn't specifically answer the questions, could anyone shed some light please?
    Tuesday, August 13, 2013 6:58 AM
  • Hi,

    Let’s run the below command to Load the specific counter:

    Program Files\Microsoft\Exchange Server\V14\Setup\Perf>lodctr activemanagerclientperfmon.ini

    Thanks,

    If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com


    Simon Wu
    TechNet Community Support

    Tuesday, August 13, 2013 5:26 PM
    Moderator
  • Thanks, I'll give this a try...

    BUT

    The original question - does this affect functionality?

    I checked the counters being reported and they are below. They all seem to be present on Mailbox servers (no errors being reported) but not CAS/HUB servers (where the errors are reported). So does that mean that they aren't actually needed because they aren't relevant to CAS/HUB servers?

    Client-side Calls ReadThrough, category name is MSExchange Active Manager Client
    Unique Budgets OverBudget, category name is MSExchange Throttling
    Items Moved to Dumpster/sec., category name is MSExchange Middle-Tier Storagethrown
    Items Dumpster Deletions/sec, category name is MSExchange Middle-Tier Storagethrown
    Dumpster Active Directory Settings cache misses., category name is MSExchange Middle-Tier Storage
    Dumpster Active Directory Settings Cache Entries, category name is MSExchange Middle-Tier Storage
    Dumpster Active Directory Settings Refresh/sec, category name is MSExchange Middle-Tier Storage
    Base counter for Dumpster Active Directory Settings cache misses., category name is MSExchange Middle-Tier Storage.
    Dumpster Active Sessions, category name is MSExchange Middle-Tier Storagethrown
    Dumpster Calendar Log Entries/sec, category name is MSExchange Middle-Tier Storage
    Folder Enumerations for Dumpster/sec, category name is MSExchange Middle-Tier Storage
    Users Delayed X Milliseconds, category name is MSExchange Throttling
    Current Delayed Tasks, category name is MSExchange Throttling.
    Unique Budgets OverBudget, category name is MSExchange Throttlingthrown
    Dumpster versions reverted on failure., category name is MSExchange Middle-Tier Storage

    Wednesday, August 14, 2013 9:40 AM
  • I have the exact same error on a new installation of Exchange 2013 SP1.  Any information on this error would be appreciated.
    Friday, May 09, 2014 9:59 PM
  • Hi,

    There is a lot of info out there on forums about possible ways to fix it, but in the end I logged case with MS Support and went through it with them. In our case they confirmed it was safe just to ignore the counter errors - everything continued to work fine since.

    I did notice that it only happens after restarting the servers or specific Exchange servers, logs loads of the events for a few days and then settles down and doesn't report them anymore.

    Support suggested that it was due to having a role on there that had been removed but the counters left incorrect. In our case the UM role had been there but removed previously - not sure if this really contributed or not but given that they said its safe to ignore we just ignored them.

    As this is a brand new install perhaps you could try some of the suggestions in other forums about reinstalling counters etc.?

    Hope that helps

    Monday, May 12, 2014 7:33 AM