Home

Error event “MSExchange Configuration Core” with ID no. 1 in the application event log every minute

%3CLINGO-SUB%20id%3D%22lingo-sub-293298%22%20slang%3D%22en-US%22%3EError%20event%20%E2%80%9CMSExchange%20Configuration%20Core%E2%80%9D%20with%20ID%20no.%201%20in%20the%20application%20event%20log%20every%20minute%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293298%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wanted%20to%20provide%20the%20solution%20to%20an%20issue%20I%20was%20troubleshooting%20this%20week.%3C%2FP%3E%0A%3CP%3EFor%20some%20time%20now%20so%2C%20a%20whole%20bunch%20but%20not%20all%20of%20the%20Exchange%202016%20servers%20were%20throwing%20this%20event%3A%3C%2FP%3E%0A%3CP%3ELog%20Name%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Application%3C%2FP%3E%0A%3CP%3ESource%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20MSExchange%20Configuration%20Core%3C%2FP%3E%0A%3CP%3EDate%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2029.11.2018%2010%3A47%3A39%3C%2FP%3E%0A%3CP%3EEvent%20ID%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%201%3C%2FP%3E%0A%3CP%3ETask%20Category%3A%20(1)%3C%2FP%3E%0A%3CP%3ELevel%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Error%3C%2FP%3E%0A%3CP%3EKeywords%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Classic%3C%2FP%3E%0A%3CP%3EUser%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20N%2FA%3C%2FP%3E%0A%3CP%3EComputer%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20MBX2016.contoso.com%3C%2FP%3E%0A%3CP%3EDescription%3A%3C%2FP%3E%0A%3CP%3EThe%20description%20for%20Event%20ID%201%20from%20source%20MSExchange%20Configuration%20Core%20cannot%20be%20found.%20Either%20the%20component%20that%20raises%20this%20event%20is%20not%20installed%20on%20your%20local%20computer%20or%20the%20installation%20is%20corrupted.%20You%20can%20install%20or%20repair%20the%20component%20on%20the%20local%20computer.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20the%20event%20originated%20on%20another%20computer%2C%20the%20display%20information%20had%20to%20be%20saved%20with%20the%20event.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20following%20information%20was%20included%20with%20the%20event%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E29464%3C%2FP%3E%0A%3CP%3Ew3wp.exe%3C%2FP%3E%0A%3CP%3EException%20from%26nbsp%3B%20CmdletHealthCountersModule.Task_Release%3A%20System.TypeInitializationException%3A%20The%20type%20initializer%20for%20'Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor'%20threw%20an%20exception.%20---%26gt%3B%20System.InvalidOperationException%3A%20Cannot%20load%20Counter%20Name%20data%20because%20an%20invalid%20index%20''%20was%20read%20from%20the%20registry.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean%20isHelp)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20System.Diagnostics.PerformanceCounterLib.get_NameTable()%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20System.Diagnostics.PerformanceCounterLib.get_CategoryTable()%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20System.Diagnostics.PerformanceCounterLib.CategoryExists(String%20machine%2C%20String%20category)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20System.Diagnostics.PerformanceCounterCategory.Exists(String%20categoryName%2C%20String%20machineName)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor..cctor()%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20---%20End%20of%20inner%20exception%20stack%20trace%20---%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor.LogActivity(CounterType%20counterType%2C%20String%20organizationName)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.ProvisioningMonitoring.PerTenantCmdletHealthCounters.UpdateSuccessCount(ErrorRecord%20errorRecord)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.CmdletHealthCountersModule.IncrementSuccessCount(ErrorRecord%20errorRecord)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.CmdletHealthCountersModule.Task_Release(Object%20sender%2C%20EventArgs%20e)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.CriticalFeatureHelper.Execute(ICriticalFeature%20feature%2C%20Action%20action%2C%20TaskContext%20taskContext%2C%20String%20methodNameInLog)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ethe%20message%20resource%20is%20present%20but%20the%20message%20is%20not%20found%20in%20the%20string%2Fmessage%20table%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEvent%20Xml%3A%3C%2FP%3E%0A%3CP%3E%3CEVENT%20xmlns%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%3C%2FA%3E%22%26gt%3B%3C%2FEVENT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%3CSYSTEM%3E%3C%2FSYSTEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CPROVIDER%20name%3D%22%26quot%3BMSExchange%22%20configuration%3D%22%22%20core%3D%22%22%3E%3C%2FPROVIDER%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CEVENTID%20qualifiers%3D%22%26quot%3B49152%26quot%3B%22%3E1%3C%2FEVENTID%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CLEVEL%3E2%3C%2FLEVEL%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CTASK%3E1%3C%2FTASK%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CKEYWORDS%3E0x80000000000000%3C%2FKEYWORDS%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CTIMECREATED%20systemtime%3D%22%26quot%3B2018-11-29T09%3A47%3A39.941532000Z%26quot%3B%22%3E%3C%2FTIMECREATED%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CEVENTRECORDID%3E9382221%3C%2FEVENTRECORDID%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CCHANNEL%3EApplication%3C%2FCHANNEL%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CCOMPUTER%3EMBX2016.contoso.com%3C%2FCOMPUTER%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CSECURITY%3E%3C%2FSECURITY%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%3CEVENTDATA%3E%3C%2FEVENTDATA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CDATA%3E29464%3C%2FDATA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CDATA%3Ew3wp.exe%3C%2FDATA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CDATA%3EException%20from%26nbsp%3B%20CmdletHealthCountersModule.Task_Release%3A%20System.TypeInitializationException%3A%20The%20type%20initializer%20for%20'Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor'%20threw%20an%20exception.%20---%26amp%3Bgt%3B%20System.InvalidOperationException%3A%20Cannot%20load%20Counter%20Name%20data%20because%20an%20invalid%20index%20''%20was%20read%20from%20the%20registry.%3C%2FDATA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean%20isHelp)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20System.Diagnostics.PerformanceCounterLib.get_NameTable()%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20System.Diagnostics.PerformanceCounterLib.get_CategoryTable()%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20System.Diagnostics.PerformanceCounterLib.CategoryExists(String%20machine%2C%20String%20category)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20System.Diagnostics.PerformanceCounterCategory.Exists(String%20categoryName%2C%20String%20machineName)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor..cctor()%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20---%20End%20of%20inner%20exception%20stack%20trace%20---%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor.LogActivity(CounterType%20counterType%2C%20String%20organizationName)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.ProvisioningMonitoring.PerTenantCmdletHealthCounters.UpdateSuccessCount(ErrorRecord%20errorRecord)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%26nbsp%3Bat%20Microsoft.Exchange.Configuration.Tasks.CmdletHealthCountersModule.IncrementSuccessCount(ErrorRecord%20errorRecord)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.CmdletHealthCountersModule.Task_Release(Object%20sender%2C%20EventArgs%20e)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.CriticalFeatureHelper.Execute(ICriticalFeature%20feature%2C%20Action%20action%2C%20TaskContext%20taskContext%2C%20String%20methodNameInLog)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%3C%2FP%3E%0A%3CP%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20beginning%20of%20the%20exception%20the%20error%20states%3A%20%E2%80%9CEither%20the%20component%20that%20raises%20this%20event%20is%20not%20installed%20on%20your%20local%20computer%20or%20the%20installation%20is%20corrupted%22%20together%20with%20%E2%80%9CCannot%20load%20Counter%20Name%E2%80%9D%3C%2FP%3E%0A%3CP%3EFrom%20the%20component%20mentioned%20in%20the%20event%20you%20can%20see%20that%20the%20component%20TenantMonitoring%20is%20affected.%3C%2FP%3E%0A%3CP%3EThe%20Process%20ID%2029464%20mentioned%20on%20the%20server%20we%20checked%20belonged%20to%20PowerShell.%3C%2FP%3E%0A%3CP%3EIn%20this%20environment%20the%20event%20was%20happening%20for%20some%20time%20and%20there%20was%20no%20inclusive%20action%20that%20could%20be%20linked%20to%20what%20caused%20the%20event%20to%20be%20thrown.%3C%2FP%3E%0A%3CP%3E%26nbsp%3BTenantMonitoring%20is%20Exchange%20internally%20used%20for%20per%20tenant%20performance%20monitoring%20although%20on%20my%20test%20Exchange%20servers%20there%20was%20not%20performance%20counter%20with%20this%20name.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20was%20not%20in%20a%20position%20to%20identify%20the%20root%20cause%20for%20this%20event%2C%20but%20the%20solution%20was%20as%20follows%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20following%20article%20describes%20how%20to%20add%20information%20for%20a%20missing%20performance%20counter%3A%3C%2FP%3E%0A%3CP%3E%22Performance%20counter%20updating%20error%22%20after%20you%20install%20an%20Exchange%20Server%202013%20cumulative%20update%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2870416%2Fperformance-counter-updating-error-after-you-install-an-exchange-serve%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2870416%2Fperformance-counter-updating-error-after-you-install-an-exchange-serve%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EThe%20procedure%20that%20stopped%20this%20event%20being%20thrown%20was%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EClose%20Performance%20Monitor%2C%20and%20then%20stop%20any%20other%20monitoring%20services%20that%20might%20be%20trying%20to%20use%20the%20missing%20counters.%3C%2FLI%3E%0A%3CLI%3EIn%20Exchange%20Management%20Shell%2C%20type%20the%20following%20command%2C%20and%20then%20press%20Enter%3A%26nbsp%3B%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EAdd-Pssnapin%20Microsoft.Exchange.Management.PowerShell.Setup%3C%2FP%3E%0A%3COL%20start%3D%223%22%3E%0A%3CLI%3ERun%26nbsp%3BNew-PerfCounters%26nbsp%3Bto%20add%20the%20performance%20counter%3A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3ENew-perfcounters%20%E2%80%93definitionfilename%20%E2%80%9CC%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CSetup%5CPerf%5CMSExchangeTenantMonitoringPerformanceCounters.xml%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20adding%20this%20performance%20counter%2C%20you%20need%20to%20reboot%20the%20Exchange%20server%2C%20in%20order%20for%20the%20change%20to%20take%20effect.%3C%2FP%3E%3CLINGO-LABS%20id%3D%22lingo-labs-293298%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Frank Plawetzki
Microsoft

I wanted to provide the solution to an issue I was troubleshooting this week.

For some time now so, a whole bunch but not all of the Exchange 2016 servers were throwing this event:

Log Name:      Application

Source:        MSExchange Configuration Core

Date:          29.11.2018 10:47:39

Event ID:      1

Task Category: (1)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      MBX2016.contoso.com

Description:

The description for Event ID 1 from source MSExchange Configuration Core cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

 

If the event originated on another computer, the display information had to be saved with the event.

 

The following information was included with the event:

 

29464

w3wp.exe

Exception from  CmdletHealthCountersModule.Task_Release: System.TypeInitializationException: The type initializer for 'Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor' threw an exception. ---> System.InvalidOperationException: Cannot load Counter Name data because an invalid index '' was read from the registry.

   at System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean isHelp)

   at System.Diagnostics.PerformanceCounterLib.get_NameTable()

   at System.Diagnostics.PerformanceCounterLib.get_CategoryTable()

   at System.Diagnostics.PerformanceCounterLib.CategoryExists(String machine, String category)

   at System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName, String machineName)

   at Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor..cctor()

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor.LogActivity(CounterType counterType, String organizationName)

   at Microsoft.Exchange.ProvisioningMonitoring.PerTenantCmdletHealthCounters.UpdateSuccessCount(ErrorRecord errorRecord)

   at Microsoft.Exchange.Configuration.Tasks.CmdletHealthCountersModule.IncrementSuccessCount(ErrorRecord errorRecord)

   at Microsoft.Exchange.Configuration.Tasks.CmdletHealthCountersModule.Task_Release(Object sender, EventArgs e)

   at Microsoft.Exchange.Configuration.Tasks.CriticalFeatureHelper.Execute(ICriticalFeature feature, Action action, TaskContext taskContext, String methodNameInLog)

 

the message resource is present but the message is not found in the string/message table

 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchange Configuration Core" />

    <EventID Qualifiers="49152">1</EventID>

    <Level>2</Level>

    <Task>1</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2018-11-29T09:47:39.941532000Z" />

    <EventRecordID>9382221</EventRecordID>

    <Channel>Application</Channel>

    <Computer>MBX2016.contoso.com</Computer>

    <Security />

  </System>

  <EventData>

    <Data>29464</Data>

    <Data>w3wp.exe</Data>

    <Data>Exception from  CmdletHealthCountersModule.Task_Release: System.TypeInitializationException: The type initializer for 'Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor' threw an exception. ---&gt; System.InvalidOperationException: Cannot load Counter Name data because an invalid index '' was read from the registry.

   at System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean isHelp)

   at System.Diagnostics.PerformanceCounterLib.get_NameTable()

   at System.Diagnostics.PerformanceCounterLib.get_CategoryTable()

   at System.Diagnostics.PerformanceCounterLib.CategoryExists(String machine, String category)

   at System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName, String machineName)

   at Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor..cctor()

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor.LogActivity(CounterType counterType, String organizationName)

   at Microsoft.Exchange.ProvisioningMonitoring.PerTenantCmdletHealthCounters.UpdateSuccessCount(ErrorRecord errorRecord)

   at Microsoft.Exchange.Configuration.Tasks.CmdletHealthCountersModule.IncrementSuccessCount(ErrorRecord errorRecord)

   at Microsoft.Exchange.Configuration.Tasks.CmdletHealthCountersModule.Task_Release(Object sender, EventArgs e)

   at Microsoft.Exchange.Configuration.Tasks.CriticalFeatureHelper.Execute(ICriticalFeature feature, Action action, TaskContext taskContext, String methodNameInLog)</Data>

  </EventData>

</Event>

 

 

In the beginning of the exception the error states: “Either the component that raises this event is not installed on your local computer or the installation is corrupted" together with “Cannot load Counter Name”

From the component mentioned in the event you can see that the component TenantMonitoring is affected.

The Process ID 29464 mentioned on the server we checked belonged to PowerShell.

In this environment the event was happening for some time and there was no inclusive action that could be linked to what caused the event to be thrown.

 TenantMonitoring is Exchange internally used for per tenant performance monitoring although on my test Exchange servers there was not performance counter with this name.

 

I was not in a position to identify the root cause for this event, but the solution was as follows:

 

The following article describes how to add information for a missing performance counter:

"Performance counter updating error" after you install an Exchange Server 2013 cumulative update

https://support.microsoft.com/en-us/help/2870416/performance-counter-updating-error-after-you-instal...

The procedure that stopped this event being thrown was:

  1. Close Performance Monitor, and then stop any other monitoring services that might be trying to use the missing counters.
  2. In Exchange Management Shell, type the following command, and then press Enter: 

Add-Pssnapin Microsoft.Exchange.Management.PowerShell.Setup

  1. Run New-PerfCounters to add the performance counter:

New-perfcounters –definitionfilename “C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\MSExchangeTenantMonitoringPerformanceCounters.xml"

 

After adding this performance counter, you need to reboot the Exchange server, in order for the change to take effect.

Related Conversations