I'm running Exchange Server 2013 on Windows Server 2012 R2, and each time I start the server I get an error event, ID 106, logged in the Application Log.  The source is MSExchange Common and the text is:

Performance counter updating error. Counter name is Current Requests Pending, category name is MSExchange LiveIdBasicAuthentication [also MSExchangeRemotePowershell, . Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly

I used a PowerShell script to reload all the performance counters, and it seemed to work for nearly all 217 .xml files in C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf.  But I still get the error when I restart the server.  Any ideas on how to fix this, what it means, or if it's safe to ignore are welcome.

Thanks!

Hi,

Please try to remove and re-create all Exchange performance counters with the following command:

add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup
$files=get-childitem C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\" *.xml |where-object {!($_.psiscontainer)}
 
foreach ($file in $files) {remove-perfcounters -definitionfilename  $file.fullname}
foreach ($file in $files) {new-perfcounters -definitionfilename  $file.fullname}

If it doesnt work, please check this KB.

http://support.microsoft.com/en-us/kb/2870416

Best Regards.

Thanks Lynn-Li.  I already ran the script from KB2870416, which looks like it does the same thing as the commands you suggest.  The event continues to pop up every time I start the virtual machine running my Exchange Server, but the condition it warns of seems harmless and Exchange Server is working fine, so I've decided this event is safe to ignore.

• Marked as answer by DBVW Architects 13 hours 51 minutes ago

Thanks Lynn-Li.  I already ran the script from KB2870416, which looks like it does the same thing as the commands you suggest.  The event continues to pop up every time I start the virtual machine running my Exchange Server, but the condition it warns of seems harmless and Exchange Server is working fine, so I've decided this event is safe to ignore.

• Marked as answer by DBVW Architects Friday, March 27, 2015 5:34 PM