Cdm Probe - RegQueryInfoKey: The system cannot find the file specified
search cancel

Cdm Probe - RegQueryInfoKey: The system cannot find the file specified

book

Article ID: 35326

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

I get max restart error with cdm probe:

I see the following log entries in my cdm log:

Jan 5 22:38:23:431 [3424] cdm: GetNameStrings - Open registry local machine key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib
Jan 5 22:38:23:431 [3424] cdm: GetNameStrings - Query registry value of Last Counter
Jan 5 22:38:23:431 [3424] cdm: GetNameStrings - lastcounter = 12060
Jan 5 22:38:23:431 [3424] cdm: GetNameStrings - Open registry local machine key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009
Jan 5 22:38:23:431 [3424] cdm: GetNameStrings - Query registry info on opened key
Jan 5 22:38:23:446 [3424] cdm: Error from GetNameStrings - RegQueryInfoKey: The system cannot find the file specified.
Jan 5 22:38:23:446 [3424] cdm: GetNameStrings - Query registry value of Counter
Jan 5 22:38:23:446 [3424] cdm: Error from GetNameStrings - RegQueryValueEx (Counter): The system cannot find the file specified.

Environment

UIM 20.4.x

Cause

Sometimes the cdm probe on Windows environments shows max restart error. The log entries indicate a problem with the perfmon counters which are used by the cdm probe. 
 

Resolution

To resolve, follow the instructions in this Microsoft post to rebuild your performance counters.

%SYSTEMROOT%\system32\lodctr /R

This command is referenced at http://support.microsoft.com/?kbid=300956
& http://support.microsoft.com/en-us/kb/2554336

Additional Information

When you use the System Monitor tool, some counters may be missing or do not contain counter data. The base set of performance counter libraries may become corrupted and may need to be rebuilt. Additionally, you may need to rebuild any custom (.NET Framework application created) counters or any extensible counters.