How to resolve WMI Monitoring Issues due to Disabled Performance Counters
Applications Manager uses WMI (Windows Management Instrumentation) for collecting performance metrics. In some cases, specific WMI classes (e.g., Win32_PerfRawData_PerfProc_Process) fail to retrieve data if performance counters are disabled in the Windows registry. This KB provides steps to identify and resolve the issue by enabling performance counters.
- Open the Run dialog (Win + R), type regedit, and press Enter.
- Go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfProc\Performance If specific attributes, such as disk, network, or operating system metrics, are unavailable, verify the following registry paths for their performance counters:
Disk:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfDisk\PerformanceNetwork:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfNet\PerformanceOperating System:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfOS\Performance
- Locate the entry named 'Disable Performance Counters' and check it's value:
- Value = 1: Counters are disabled
- Value = 0: Counters are enabled
- If the value is set to "1", double-click it and change the value to "0".
- Restart Applications Manager for the changes to take effect.
- If the Disable Performance Counters registry key is not present, it indicates that Performance Counters have not been explicitly disabled in the registry.
- Applications Manager support does not provide assistance for issues resulting from improper registry modifications. The Windows registry stores critical information essential for your computer and applications. To avoid potential issues, ensure you back up the registry before making any changes.
- Ensure you have administrative privileges to edit the registry.
- For large-scale environments, confirm that performance counters are enabled on all monitored servers.
- For detailed instructions on using the Windows Registry Editor and guidance on backing up and restoring it, refer to the Microsoft Support article titled Windows registry information for advanced users.
New to ADSelfService Plus?
Related Articles
Configuring non-admin user account for WMI monitoring
By default, Windows allows only members of the Administrators or Domain Admin groups to read WMI class information. However, you can configure a regular user to access WMI information by performing the following steps on the server that needs to be ...Getting 'Invalid WMI query' with error code 0x80041017 in Windows
"Invalid WMI query" with error code WBEM_E_INVALID_QUERY (0x80041017) found in log files or script execution when collecting Windows performance counter data. It is possible that the Win32_PerfRawData_PerfOS_Processor cannot be found or accessed on ...Setting WMI access through Active Directory and Group Policy Object for non-admin user
In our case, we run Active Directory on Windows 2008 R2 and we want to scan the target machine which is Windows 2012 R2 machine. Our domain is called “APMCLU” and we name our dedicated WMI user-account “wmiuser”. First – Setting done from Active ...Troubleshooting Basic WMI Connection
Troubleshoot Basic WMI connectivity If you're using Applications Manager version 15470 or above, navigate to Admin > Self Help Tools and select the monitor type to troubleshoot the issue. Click here for more details. If you encounter an error in the ...Troubleshooting steps to identify and resolve the `System.AccessViolationException` crashing issue while monitoring the .NET applications
Understanding Our .NET agent instrumentation may encounter issues with specific versions of framework methods in your .NET applications, resulting in disruptions to the application monitoring process. If you encounter the exception ...