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?
Let’s run the below command to Load the specific counter:
Program Files\Microsoft\Exchange Server\V14\Setup\Perf>lodctr activemanagerclientperfmon.ini
If you have feedback for TechNet Subscriber Support, contact email@example.com
TechNet Community Support
Thanks, I'll give this a try...
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
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
This Performance Counter Updating Error is a common problem.......This generally encountered when restarting the new server after the installation of Exchange Server 2013 CAS roles.......Please use the script method to solve this error....Script method has been explained in this blog...please take a look at this blog ......
Hope, this may be helpful for you.