Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Server & Application Monitor (SAM) > Performance counters are not working or missing in PerfMon

Performance counters are not working or missing in PerfMon

Table of contents

Updated December 14, 2017

Overview

This article describes the following issues with performance counters when they are not working properly:

  • Invalid class errors are displayed
  • WMI or PerfMon counters show as down even when they are up

 

To see a video on recovering performance counters that are not working or missing in PerfMon, go here.

Environment

All SAM version on Windows Server 2003 and later

Steps

Rebuild the performance counters:

  1. Open a command prompt as an administrator on the target server and enter the following commands:
    • cd %windir%\system32\
    • lodctr /R
    • cd %windir%\sysWOW64\
    • lodctr /R
      Note: These commands will re-synchronize the counters and does not have an effect on the performance of the machine.
  2. Open regedit and go the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfProc\Performance
  3. Search for Disable Performance Counters and make sure that the value is not 1. You can either change the value to 0 or delete the entry.
    Note: Create a backup of the entry and contact your system administrator before making changes to the registry.
  4. Restart the Windows Management Instrumentation service.

 

If the above procedure fails, manually rebuild the performance counter values (© Microsoft, available at https://support.microsoft.com/, obtained on July 19, 2017.), and then reboot your machine.

Follow the instructions in this THWACK post if you are working with a Cold Fusion server.
If these procedures fail, please contact Microsoft in order to resolve the issue with the server.  

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified

Tags

Classifications

Public