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.

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

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

   winmgmt /resyncperf
   wmiadap /f

\n
2. In the up.time UI, browse to the Windows element, select the small Services tab, and click Manage Services. Select the Platform Performance Gatherer from the list and then click the Test Service Monitor button.
\n
3. If the status is OK and the message contains the version of the up.time Agent, the counters are being returned as expected and you can stop here; otherwise, please proceed to step 2.
\n
\n \n
• Rebuild the counters
\n
\n
1. Run the `lodctr /S` command as the local administrator to save the current performance registry settings and counters.
   \n

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

\n \n
2. Run `lodctr /r` 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.
   \n
   \n
   • Stop the Windows Management Instrumentation service.
   \n
   • Open a command prompt as local administrator and run the command `lodctr /r`.
   \n
   • Start the Windows Management Instrumentation service.
   \n
   \n
\n
3. In the up.time UI, browse to the Windows element, select the small Services tab, and click Manage Services. Select the Platform Performance Gatherer from the list and then click the Test Service Monitor button.
\n
4. If the status is OK and the message contains the version of the up.time Agent, the counters are being returned as expected and you can stop here; otherwise, please proceed to step 3.
\n
\n \n
• Submit material to Support

  \nIf, after rebuilding the counters, the issue persists, please perform the following steps and send the files into uptime Support at [email protected] for further investigation.

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

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

\n \n
2. Email to [email protected] both lodctr output files (saved.txt and savedafter.txt), as well as the output from Poll Agent or Poll WMI.
   \n
   \n
   • Browse to the Windows element in the up.time UI.
   \n
   • Select the Info tab and click Poll Agent or Poll WMI in the list on the left.
   \n
   • Copy the Poll Agent/WMI output into a text file and send in to uptime Support along with the lodctr output files.
   \n
   \n
\n
\n

References