Juszeil Conception
2023-3-24 
| 
| BLOG 部落格
Total found 1 articles on 2016-5-19.
After you install the Microsoft Exchange Server 2013 Client Access server role on a new server and then restart the server, you receive many Event ID 106 errors in the Application log. For example, you may receive the following error message:
When you check the Exchange Setup log (ExchangeSetup.log), you see the following information:
This issue occur because the performance counters cannot be loaded.
Relate Post : Exchange 2013 - How to force OWA regional language settings Exchange 2013 - Archiving Emails Exchange 2013 Enable Anti Spam Exchange 2013 - Add An Administrator Exchange 2013 - DAG Cluster tunning 摰鋆 Office Web Apps Server 2013 (OWA) Exchange 2013 - Recreate Health Mailboxes Exchange 2010/2013 - OWA allow Users to Change Expired Passwords Exchange 2010 - DAG CAS Array Exchange 2013 - Client Access Server High Availability
Comments :
No Comments
銵 2016-5-19 17:21:42
Exchange 2010/2013 - Error 106
After you install the Microsoft Exchange Server 2013 Client Access server role on a new server and then restart the server, you receive many Event ID 106 errors in the Application log. For example, you may receive the following error message:
ID: 106
Level: Error
Source: MSExchange Common
Machine: -
Message: Performance counter updating error. Counter name is Per-Tenant KeyToRemoveBudgets Cache Size, category name is MSExchangeRemotePowershell. Optional code: 3. Exception: The exception thrown is: System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.\
Level: Error
Source: MSExchange Common
Machine: -
Message: Performance counter updating error. Counter name is Per-Tenant KeyToRemoveBudgets Cache Size, category name is MSExchangeRemotePowershell. Optional code: 3. Exception: The exception thrown is: System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.\
When you check the Exchange Setup log (ExchangeSetup.log), you see the following information:
[WARNING] The performance counter definition file C:\Program Files\Microsoft\Exchange Server\V15\Bin\Perf\AMD64\GlsPerformanceCounters.xml could not be found.
Cause
Resolution
To resolve this issue, use one of the following methods.
Note Although either of these methods will resolve the issue, event ID 106 from MSExchange Common will never truly be eliminated from on-premises deployments because some counters are datacenter-only.
Note Although either of these methods will resolve the issue, event ID 106 from MSExchange Common will never truly be eliminated from on-premises deployments because some counters are datacenter-only.
Use a script to reload all the performance counters
- Copy the following script to Notepad, and then save the file as Perfcounters.ps1. Make sure that you change the "$path" value in the script if the Exchange Server is installed in a different location. (This script also applies to Exchange Server 2010.)
add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup $path = "C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf" $items = Get-ChildItem -Recurse $path $files = $items | ?{$_.extension -eq ".xml"} Write-Host "Registering all perfmon counters in $path" 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 } - In Exchange Management Shell, run the file that you created in step 1. For example, run the following command:
c:\perfcounters.ps1
The Problem will be fix.
Relate Post : Exchange 2013 - How to force OWA regional language settings Exchange 2013 - Archiving Emails Exchange 2013 Enable Anti Spam Exchange 2013 - Add An Administrator Exchange 2013 - DAG Cluster tunning 摰鋆 Office Web Apps Server 2013 (OWA) Exchange 2013 - Recreate Health Mailboxes Exchange 2010/2013 - OWA allow Users to Change Expired Passwords Exchange 2010 - DAG CAS Array Exchange 2013 - Client Access Server High Availability
Comments :
No Comments
Post your comment:
Back To Top
