Update: 09.06.2013 Updated the PowerShell script and some additional information about event logs. /tom

Today I installed 4 Exchange 2013 servers. 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. Counter name is LDAP Queries Issued by Expanded Groups., category name is Expanded Groups Cache. 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

The problem is that the performance counters are not registered correctly. I wrote a simple script to re-register all the Exchange 2013 performance counters. Now the Application log looks much better Smiley

First open Powershell in Admin Mode, then execute the following code:

Note that New-PerfCounters actually deletes and re-creates the performance counter, there is no need to use Remove-PerfCounters 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. 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.

Special thanks to @msxfaq :)



This post has been migrated from our earlier blog based on BlogEngine.NET.