And that typo is the reason why the eventlogs are filling up with event id 106 error's faster than you can blink an eye.
There is a Technet Article showing you how to update the Performance counter all at once with a PowerShell script, but if you do this then you get the following error:
Well that doesn't help, But now we know which performance counter to deal with.
Let's have a look at the file it self:
Open C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml
In there you have to search for: "> Searches"
The one space is causing all the trouble.
Find/replace "> Searches" with ">Searches" and save the file on all your exchange 2013 Servers.
-Note This seems to be going on from the RTM up to CU12, so don't think i've got the most recent CU so i'm fine, no your not, this is one of the many issues that just don't ever get fixed until the Office365 team or the Exchange dev team wants to or get's told to do so.
In the mean time use this.
After the file has been saved on all Exchange 2013 servers go to the EMS:
[PS] C:\windows\system32>Add-Pssnapin Microsoft.Exchange.Management.PowerShell.Setup [PS] C:\windows\system32>New-PerfCounters -definitionfilename "C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf \InfoWorkerMultiMailboxSearchPerformanceCounters.xml" [PS] C:\windows\system32>