Error Message

Event ID: 41382 Health check received timeout exception. The indexing engine will be restarted.

{ESHealthMonitor.Start} Exception: Invalid performance counter data with type 'PERF_OBJECT_TYPE'. Info:Failed to start Elasticsearch Health Monitoring Tasks Diag: Type:System.InvalidOperationException ST:   at Microsoft.Win32.NativeMethods.ThrowInvalidOperationException(Type type)|   at Microsoft.Win32.NativeMethods.PERF_OBJECT_TYPE.Validate(Int32 bufferSize)|   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 Veritas.EnterpriseVault.Indexing.Admin.ESMonitoring.ESPerformanceCounters..ctor()|   at Veritas.EnterpriseVault.Indexing.Admin.ESMonitoring.ESPerformanceCounters.<>c.<.cctor>b__11_0()|   at System.Lazy`1.CreateValue()|--- End of stack trace from previous location where exception was thrown ---|   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()|   at System.Lazy`1.LazyInitValue()|   at Veritas.EnterpriseVault.Indexing.Admin.ESMonitoring.ESJVMHeapUsageMonitorTask.TaskMain()|   at Veritas.EnterpriseVault.Indexing.Admin.ESMonitoringTaskBase.TaskMainWrapper() Inner:None

V-437-41382

Event ID: 41309 The following error message occurred in the core indexing engine: Failed to communicate with Elasticsearch indexing engine. Try restarting the Indexing Service to fix the issue.

V-437-41309

Event ID: 41293 An unexpected error has occurred.|Error Summary: Indexing Service start up error |Error Details: Invalid performance counter data with type 'PERF_OBJECT_TYPE'. |Reference: ServiceBaseEx::Run |Stack Trace:    at Microsoft.Win32.NativeMethods.ThrowInvalidOperationException(Type type)|   at Microsoft.Win32.NativeMethods.PERF_OBJECT_TYPE.Validate(Int32 bufferSize)|   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 Veritas.EnterpriseVault.Indexing.Admin.ESMonitoring.ESPerformanceCounters..ctor()|   at Veritas.EnterpriseVault.Indexing.Admin.ESMonitoring.ESPerformanceCounters.<>c.<.cctor>b__11_0()|   at System.Lazy`1.CreateValue()|--- End of stack trace from previous location where exception was thrown ---|   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()|   at System.Lazy`1.LazyInitValue()|   at Veritas.EnterpriseVault.Indexing.Admin.ESMonitoring.ESJVMHeapUsageMonitorTask.TaskMain()|   at Veritas.EnterpriseVault.Indexing.Admin.ESMonitoring.ESHealthMonitor.Start()|   at Symantec.EnterpriseVault.Indexing.Admin.IndexAdminService.OnPerformStartup(Boolean HotRestart)|   at KVS.EnterpriseVault.Common.ServiceBaseEx.Run()

V-437-41293

This issue is caused when some or all of the Enterprise Vault Index Performance Counters are missing and/or corrupt. 

Note: The above performance counter image should include:

• Enterprise Vault Index Query Server
• Enterprise Vault Indexing (Elasticsearch)
• Enterprise Vault Indexing Volumes Processing

Launch the registry 

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

Ensure that the following Keys are present

• Enterprise Vault Index Query Server 
• Enterprise Vault Indexing (Elasticsearch)
• Enterprise Vault Indexing Volumes Processing 

Then within each Key, verify the Linkage and Perfmrnace Keys are present:

Highlight each Linkage Key and ensure that there is a Multi-String Value with the name of the parent Key. For example the Linkage Key under Enterprise Vault Index Query Server should have a Multi-String Value entry named Enterprise Vault Index Query Server, the Linkage Key under Enterprise Vault Indexing (Elasticsearch) should have a Multi-String Value entry named Enterprise Vault Indexing (Elasticsearch), and the Linkage Key under Enterprise Vault Indexing Volumes Processing should have a Multi-String Value entry named Enterprise Vault Indexing Volumes Processing.

Highlight each Performance Key and ensure that the following Values are present 

• CategoryOptions (RegDWord)
• Close (String Value)
• Collect (String Value)
• Counter Names (Multi-String Value)
• Counter Types (Multi-String Value)
• First Counter (RegDWord)
• First Help (RegDWord)
• IsMultiInstance (RegDWord)
• Last Counter (RegDWord)
• Last Help (RegDWord)
• Library (String Value)
• Object List (String Value)
• Open (String Value)
• PerfIniFile (String Value)

Once the registry entries are repaired or updated, launch a command prompt, using Run As > Administrator. 

• Navigate to C:\Windows\SysWOW64
• Type lodctr /R
• Type Winmgmt.exe /RESYNCPERF