On a new server the CDM probe is sending the following alarm: "InternalAlarm: Unable to get CPU data (error)" What can we do to resolve this issue?
search cancel

On a new server the CDM probe is sending the following alarm: "InternalAlarm: Unable to get CPU data (error)" What can we do to resolve this issue?

book

Article ID: 6368

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

On a new server the CDM probe is sending the following alarm:
"InternalAlarm: Unable to get CPU data (error)"
What can we do to resolve this issue?


I have already run through the full Repair Windows performance counter steps from the Windows site followed up with a reboot but did not work.

I also ran a full windows update and reboot and did not help.

 
For reference the rebuilt steps are:
---------------------------
To rebuild all Performance counters including extensible and third-party counters, type the following commands at an Administrative command prompt. Press ENTER after each command.

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.

Environment

UIM 8.47CDM 5.61-5.80robot / Controller 7.xThe box is a Physical Server a HP Proliant DL580 running Windows Server 2008 Standard Edtion 64-bit.

Cause

The system was missing performance counters.

 

Resolution

the windows 2000 resource utility kit had a tool called "Extensible Performance Counter List"
Client copied this tool out of the tool kit and uploaded to target server :

can download from MS:
https://blogs.technet.microsoft.com/askperf/2010/03/04/two-minute-drill-disabled-performance-counters-and-exctrlst-exe/

Client then ran as admin then checked all counter statuses and noticed that the perfos.dll enabled check box was off.
Client then changed it to enable it.
then opened performance monitor and noticed they no longer were getting MMC error when opening
next they re-ran the counter rebuild commands and that fixed the issue.