Event ID 106, Source MSExchange Common, Level Error: Log Name: Application Source: MSExchange Common Date: 24.1.2011 Event ID: 106 Task Category: General Level: Error Keywords: Classic User: N/A Computer: Server local Description: Performance counter updating error. Invalid Operation Exception: The requested Performance Counter is not a custom counter, it has to be initialized as Read Only. Counter name is RPC Requests, category name is MSExchange Rpc Client Access. (Counter, Category, and Exception message vary): Performance counter updating error.
Counter name is Power Shell Average Response Time, category name is MSExchange Remote Powershell. The issue is caused by an error in the Exchange setup process where a performance counter definition is tried to read from the wrong location. Copy the following script to a text file and save with the .ps1 extension. If you run into issues you can manually retry the process for that specific performance counter definition.
New-perfcounters definitionfilename "C:\Program Files\Microsoft\Exchange Server\V14\Setup\Perf\Rpc Client Access Performance Counters.xml" Ref: Blog about adding missing performance counters in Exchange 2010: EV100379 (How to unload/reload performance counters on Exchange 2010).
Another mysterious error after installing Exchange 2013.
ID: 106 Level: Error Source: MSExchange Common Machine: - Message: Performance counter updating error. Invalid Operation Exception: The requested Performance Counter is not a custom counter, it has to be initialized as Read Only.\ add-pssnapin Microsoft. He have a Data Technician degree from Denmark, Copenhagen, where he also live and work.
Counter name is Per-Tenant Key To Remove Budgets Cache Size, category name is MSExchange Remote Powershell. His goal is to be a MVP in digital technology industry.