DX Infrastructure Management

 View Only

cdm - Unable to get CPU data (error) 

Aug 07, 2015 05:40 AM

This issue has been reported on the 'cdm' probe v5.31t on win2008R2 server but has been also reproduced with v5.21 and v5.41.

 

When running the probe gets this kind of error messages:

- cdm: ntgetuptime: Unable to get the 'System Up Time' counter of the 'System' performance object

- cdm: GetHostInfo - unable to get system uptime

 

With the alarm in the console:

InternalAlarm: Unable to get CPU data (error)

 

Solution:

Reset all the performance counter by executing 'lodctr /r ' in command prompt.

Restart the probe.

Statistics
0 Favorited
10 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Oct 05, 2017 07:17 AM

Just had this one on a Win 2008 Server running CDM version 6.20 - ran the command - restarted the probe, time will tell if it's worked or not.

Jul 13, 2017 05:34 PM

What if we did every possible thing here:

Rebuilding the counters:
     cd c:\windows\system32
     lodctr /R
     cd c:\windows\sysWOW64
     lodctr /R
Resyncing the counters with Windows Management Instrumentation (WMI):
     WINMGMT.EXE /RESYNCPERF
Stop and restart the Performance Logs and Alerts service. 
Stop and restart the Windows Management Instrumentation service.

And still the cdm probe is throwing this error after running above, rebooting the box, restarting the probe, and service.

Even tried using the exctrlst.exe diagnostic repair tool to rebuild the dll's on the target box and still no good.

 

Jan 04, 2017 07:53 AM

Yes, on each Server due local Microsoft OS issue.

Dec 23, 2016 10:20 AM

Error code 5 is a permissions issue.  Use RunAs Administrator and that "should" take care of it.

Dec 22, 2016 10:51 AM

I am getting below error when tried to run this command.

 

Error: Unable to rebuild performance counter setting from system backup store, error code is 5

 

Kindly suggest.

 

Regards,

IK

Dec 22, 2016 10:47 AM

Do we need to run this command in the command prompt of every server where we are facing this issue or on the hub server?

Related Entries and Links

No Related Resource entered.