Annoying Event ID 106 MSExchange Common Exchange 2016

Question

_{Tuesday, January 17, 2017 1:37 PM}

Hi all,

I know that this event and problem was spread a lot and a lot of suggestions were made. I've already tried re-importing the performance counters but the event is still appearing and we have a really huge number of warnings from it:

for the last 24 hours we have 41 864 events - this is really big number.

I've used this 

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Setup
Get-ChildItem "$exInstall\Setup\Perf" `
   | Where-Object {$_.Name -match ".xml"} `
   | Foreach { 
         Write-host "Importing " $_.fullname
          New-PerfCounters -DefinitionFileName $_.FullName
      }

and this 

Add-PsSnapin Microsoft.Exchange.Management.PowerShell.Setup
$files = Get-ChildItem $exinstall\setup\perf\.xml
Write-Host "Registering the perfmon counters"
Write-Host
$count = 0;
foreach ($i in $files)
{
   $count++
   $f =  $i.directory, "\, $i.name -join ""
   Write-Host $count $f -BackgroundColor red
   New-PerfCounters -DefinitionFileName $f
}

I've checked also this dir: C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf

but the counters and and category name are not listed in this folder. For example:

Performance counter updating error. Counter name is Percentage of Failed Offline GLS Requests in Last Minute, category name is MSExchange Global Locator OfflineGLS Processes. Optional code: 3. Exception: System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.

Performance counter updating error. Counter name is Percentage of MSAUserNetID Cache hits for last minute, category name is MSExchange Global Locator Processes. Optional code: 3. Exception: System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.

Performance counter updating error. Counter name is Percentage of ExternalDirectoryOrganizationId Cache hits for last minute, category name is MSExchange Global Locator Processes. Optional code: 3. Exception: System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.

Performance counter updating error. Counter name is Percentage of domain Cache hits for last minute, category name is MSExchange Global Locator Processes. Optional code: 3. Exception: System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.

We are running Exchange Server 2016 CU3 .

Does someone could help?

Thanks

All replies (8)

_{Wednesday, January 18, 2017 7:36 AM}

Hi SOWITEC,

This issue occurs because the performance counters cannot be loaded.

We can refer to the following blog and check if any helps:

Fix for Performance Counter Updating Error (Event 106) on Exchange Servers

Solution:

You can run the following script directly on the affected Exchange server from an elevated PowerShell or EMS prompt. The script will reload all the performance counters in the %ExchangeInstallPath%\setup\perf directory.

**Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Setup
$perfcounters = Get-ChildItem "$env:ExchangeInstallPath\Setup\Perf\ *.xml | Where-Object {!($_.psiscontainer)}
$perfcount = $perfcounters.Count

foreach ($perfcounter in $perfcounters) {
New-PerfCounters -DefinitionFileName  $perfcounter.FullName -ErrorAction SilentlyContinue
        Write-Progress -Activity "Reloading $perfcount Exchange Performance Counters" -PercentComplete (($i++ / $perfcount) * 100)}**

Hope this helps,

Best Regards,

Niko Cheng
TechNet Community Support

Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, January 19, 2017 2:25 PM}

Hi Niko,

I've tested the script - it run and the 106 are still coming, since the script we have 10 902 Events.

_{Sunday, January 22, 2017 12:07 PM}

Hi Niko,

there is a progress in this issue. I used this article : 

http://www.ftpnet.de/2016/06/29/event-106-msexchange-common-exchange-2016/

and after this the number of event 106 was greatly reduced - from 10 to 2 per appearance. The remaining 2 events are:

Performance counter updating error. Counter name is Percentage of total GLS Requests served by Offline GLS in Last Minute, category name is MSExchange Global Locator OfflineGLS Processes. Optional code: 2. Exception: System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.get_RawValue()
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()

Performance counter updating error. Counter name is Percentage of Failed Offline GLS Requests in Last Minute, category name is MSExchange Global Locator OfflineGLS Processes. Optional code: 3. Exception: System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.get_RawValue()
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)

_{Wednesday, February 8, 2017 6:57 AM}

Hi SOWITEC,

Based on my research, the GLS counters which are mentioned in the remaining events, are used in the tasks "ExchangeDiagnosticsDailyPerformanceLog" & "ExchangeDiagnosticsPerformanceLog" , as below:

We can ignore these events safely, as these counters are not custom counters, and do not exist in "C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf" folder; Or we can remove these counters from the tasks and check if the events are still generated.

Best Regards,

Niko Cheng
TechNet Community Support

Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Friday, March 17, 2017 8:57 AM}

Hi Niko,

I've removed the 2 counters and will reboot the server on Saturday. After this I will let you know. 

I know that we could ignore them but 41886 Events for 30 days are too much from pov. When the logs are flooded than it will hard to see other events.

_{Saturday, March 18, 2017 9:55 AM}

Hi Niko,

I've removed them and the server was rebooted. Unfortunately they appeared again, so I removed them and stop/start the collector. This didn't helped as well - the events are still logged. Can I remove also the third counter? Should I also remove the counters from the exchange folder or run lodctr ?

thanks in advance

_{Wednesday, March 29, 2017 12:37 PM}

Hi Niko,

do you have more ideas ?

_{Tuesday, August 22, 2017 8:36 AM}

After installing CU6 the event stopped.