If you suspect that the performance counters on a Windows system are corrupt, your system administrator will need to rebuild or reload the default performance counter library values on that system. Indications of corrupt performance counters can include drastically incorrect values (ex. total cpu usage exceeding 100%), missing counters, or Perflib event log errors. For related articles review: "more information, see No recent performance data available. Is the system online? "
- message in WMI elements and "No recent performance data available. Is the system online? " - message in Uptime Infrastructure Monitor Agent agent Windows elements.

The first and easiest step is to refresh the performance counters. If that does not work, then rebuilding the counters is required. 

...

Refresh

...

the performance counters

To refresh the performance counters

1. On the Windows system, run the following commands on the command line to refresh the performance counters.
   

   Code Block
   language sql
   winmgmt /resyncperf wmiadap /f

2. In the Uptime Infrastructure Monitor UI, browse to the Windows element, select .
3. Select the small Services tab, and then click Manage Services.
4. Select the Platform Performance Gatherer from the list, and then click the Test Service Monitor button.
5. If the status is OK and the message contains the version of the Uptime Infrastructure Monitor Agent, the counters are being returned as expected and you can stop here; otherwise, please proceed to step 2continue with Rebuild the counters.

Rebuild the

...

counters

1. Run the `lodctr lodctr /S` S command as the local administrator to save the current performance registry settings and counters.
   

   Code Block
   language sql
   cd "%PROGRAMFILES(X86)%uptime softwareup.time agent" lodctr /S:saved.txt

2. Run `lodctr the lodctr /r` S command to rebuild the counters on the target host. It is recommended, if possible, to back up the Windows element before performing this task as a precautionary measure.

   ...

   1. 1. Stop the Windows Management Instrumentation service.

   ...

   1. 1. Open a command prompt as local administrator and run the command

   ...

   1. 1. lodctr /

   ...

   1. 1. r.

   ...

   1. 2. Start the Windows Management Instrumentation service.
   2. In the Uptime Infrastructure Monitor UI, browse to the Windows element, select .
   3. Select the small Services tab, and click then click Manage Services.
   4. Select the Platform Performance Gatherer from the list, and then click the Test Service Monitor button.
   5. If the status is OK and the message contains the version of the Uptime Infrastructure Monitor Agent, the counters are being returned as expected and you can stop here; otherwise, please proceed to step 3continue with Submit material to Support.

   Submit material to Support

   If, after rebuilding the counters, the issue persists, please perform the following steps and send the files into Support at uptime-support@idera.com for further investigation.

   1. Run the `lodctr /S` command as local administrator again, so Support can compare the before and after files.
      

      Code Block
      language sql
      cd "%PROGRAMFILES(X86)%uptime softwareup.time agent" lodctr /S:savedafter.txt

   2. Email to uptime-support@idera.com both lodctr output files (saved.txt and savedafter.txt), as well as the output from Poll Agent or Poll WMI.
      1. Browse to the Windows element in the Uptime Infrastructure Monitor UI.
      2. Select the Info tab and click Poll Agent or Poll WMI in the list on the left.
      3. Copy the Poll Agent/WMI output into a text file and send in to Support along with the lodctr output files.

   ...

   References

   ...