106 performance counter updating error

Although this notification is pretty harmless, it’s still amazingly annoying. To solve this error, we need to modify an XML file, and then rebuild the performance counter. You might experience some errors in Application log after Microsoft Exchange RPC Client Access service is started. Performance Counter.set_Raw Value(Int64 value) at Microsoft. Win32Error(Int32 error Code, String str) at Microsoft. Let’s try to manually add RPC Client Access performance counters. Create Sub Key(String subkey, Registry Key Permission Check permission Check, Registry Security registry Security) at Microsoft. It’s not so pretty to see many errors in Event Viewer after restarting Microsoft Exchange RPC Client Access service. However, this does not affect the functionality of the Exchange Server 2010 server. Get Last Worker Process Info()This problem occurs because the performance counters of the RPC Client Access service are not installed when you install only the Mailbox role on an Exchange Server 2010 server.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.

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. Fehler beim Aktualisieren eines Leistungsindikators. Der Indikatorname lautet ‚Percentage of MSAUser Net ID Cache hits for last minute‘, der Kategoriename ist ‚MSExchange Global Locator Processes‘. Invalid Operation Exception: Der angeforderte Leistungsindikator muss als Read Only initialisiert werden, da er nicht benutzerdefiniert ist. 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.

Counter name is Per-Tenant Key To Remove Budgets Cache Size, category name is MSExchange Remote Powershell. This issue occur because Exchange Server Setup tries to locate the Gls Performance performance counter definition file in the following folder: C:\Program Files\Microsoft\Exchange Server\V15\Bin\Perf\AMD64\ However, Exchange Server Setup should target the following folder instead: C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf Therefore, the performance counters cannot be loaded.