Performance counter not updating
For more information, see counter displays the number of exceptions thrown in an application, because these can have performance implications.However, some code paths rely on exceptions for proper functioning.
A high number for this counter usually indicates either high contention in locks or many switches by the thread between user and kernel modes.If you experience this, you should investigate further with sampling profilers and other tools. An application restart can occur because of changes to the Web.config file, changes to assemblies stored in the application's Bin directory, or when an application must be recompiled due to numerous changes in ASP. Unexpected increases in this counter can mean that problems are causing your Web application to recycle.In such circumstances you should investigate as soon as possible.The number of requests waiting for service from the queue.Event ID 1001 indicates that the counter has been removed, while Event ID 1000 is logged as soon as the counter has been loaded again.If an antivirus software is running on the server, it could be disabled temporarily to improve performance.
The value associated with each performance counter is updated every 400 milliseconds.
When creating a monitoring application, be sure to take this time lapse into account so that your code does not use an obsolete counter value.
Update: Updated the Power Shell script and some additional information about event logs. All of them have many “MSExchange Common” 106 errors in the Application Log indicating that Performance Counters could not be updated: Performance counter updating error. Invalid Operation Exception: The requested Performance Counter is not a custom counter, it has to be initialized as Read Only The problem is that the performance counters are not registered correctly.
Counter name is LDAP Queries Issued by Expanded Groups., category name is Expanded Groups Cache. I wrote a simple script to re-register all the Exchange 2013 performance counters.
Now the Application log looks much better First open Powershell in Admin Mode, then execute the following code: Note that New-Perf Counters actually deletes and re-creates the performance counter, there is no need to use Remove-Perf Counters first.
The script might throw some errors if performance counters cannot be created or files are invalid, other than that no information is displayed, no news is good news, I guess ;) For more information check the Application Log of the server, two events are logged for every performance counter.