Problem: Exchange 2010, 2008R2, Event 106 MSExchange Common
Solution: Reload the correct performance counter file in Powershell
Event 106, MSExchange Common |
Performance counter updating error. Counter name is Base for Average Number of Mailboxes Processed per Request, category name is MSExchange Availability Service. Optional code: 1. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly. at System.Diagnostics.PerformanceCounter.Initialize() at System.Diagnostics.PerformanceCounter.IncrementBy(Int64 value) at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.IncrementBy(Int64 incrementValue) Last worker process info : System.UnauthorizedAccessException: Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\Transport' is denied. at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str) at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck, RegistrySecurity registrySecurity) at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo() Processes running while Performance counter failed to update: 2164 MSExchangeMailSubmission |
Get the "D:\Program Files\Microsoft\Exchange Server\V14\Setup\Perf" path
Open Exchange Powershell:
Add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup
D:\Program Files\Microsoft\Exchange Server\V14\Setup\Perf\RpcClientAccessPerformanceCounters.ini
[PS] C:\ >Add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup [PS] C:\ >New-perfcounters -definitionfilename "D:\Program Files\Microsoft\Exchange Server\V14\Setup\Perf\RpcClientAccessPerformanceCounters.xml" [PS] C:\ > |
Event 1000, Source LOADPERF > OK |
Performance counters for the MSExchange RpcClientAccess (MSExchange RpcClientAccess) service were loaded successfully. The Record Data in the data section contains the new index values assigned to this service. |
If this does not fix try following (Correct the paths again) |
Add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup
|
Your worst case scenario in terms of risk would be at the end if all does not solve it you have to re-index the Exchange Databases.
In would wait with that UNTIL you check all the Permissions/Counters and if they are registered correct!
Here is the official Linkl for the RE-INDEX (Last options if it currently fails all of the time)