Question : WinMgmt   win adap event id:37 Error

I am using windows 2000 professional and I am getting this Error everytime I start using my Adobe Golive.  This error has never occurred before I loaded this on my maching.  I have read a few things about this error. I relize it is a windows 2000 problem but is there a fix?

Answer : WinMgmt   win adap event id:37 Error

You may have already read this KB article on the error, but here it is. I was getting the same error messages as well on my systems. Dredging the system's performance libraries was a temporary fix and the problem would re-surface. Once I made the registry changes noted below, I have yet to see the error resurface (Crossing fingers)

Craig
----------------------

Troubleshooting WinMgmt-Based Performance Counter Errors

--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Windows 2000 Server
Microsoft Windows 2000 Professional

--------------------------------------------------------------------------------
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.


SYMPTOMS
When you view the Application Event Viewer log on your computer, you may see one or more of the following entries:

Event Type: Error
Event Source: WinMgmt
Event Category: None
Event ID: 37
Description: WMI ADAP was unable to load the file name performance library due to an unknown problem within the library: 0x0

Event Type: Error
Event Source: WinMgmt
Event Category: None
Event ID: 41
Description: ADAP was unable to process the file name performance library due to a time violation in the collect function

Event Type: Error
Event Source: WinMgmt
Event Category: None
Event ID: 61
Description: WMI ADAP was unable to process the file name performance library due to a time violation in the open function



CAUSE
These events can be logged either because of a problem in the counter, or a false positive return value in the Windows Management Instrumentation (WMI) Performance Library Dredger. In the latter instance, in certain situations, the dredger incorrectly determines that a library is invalid even though the counter works correctly.



WORKAROUND
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

First, try once more to dredge the system's performance libraries using the following commands:

WINMGMT /CLEARADAP
This command clears all Web-Based Enterprise Management (WBEM) related values from the service's performance registry key.
WINMGMT /RESYNCPERF "winmgmt service PID"
This command registers the the system's performance libraries with the WMI.

The WMI service PID information can be found in the Process tab of Windows Task Manager.

The performance registry keys of the involved services are:

WbemAdapFileSize
WbemAdapFileTime
WbemAdapStatus

Note: For more information about the command line options available with WMI, type winmgmt/? at a command prompt.

Another possible reason for the above events may be that the counters are slow to respond due to other activities during startup. It is possible to tune this timeout by adding the value Collect Timeout REG_DWORD 10000 to the appropriate registry location:
HKey_Local_Machine\System\CurrentControlSet\Services\[counterfile]\Performance
If events continue to be logged after making the above changes, change the WbemAdapStatus value manually to REG_DWORD 0 under the service's performance registry key and increase the ADAPPerflbTimeout value to REG_DWORD 180 under the following registry key:
HKLM\Software\Microsoft\Wbem\CIMOM
Note: All registry changes have to be entered as decimal values.

In addition, it is possible to disable performance counters for a specific service with the Exctrlst.exe utility from the Windows 2000 Resource Kit.
This utility disables the specific counter by adding a registry key similar to the example below. These registry entries can be added under the specific counter entry manually if Exctrlst.exe is not available or desirable.
HKLM\System\CurrentControlSet\Services\Spooler\Performance

Value Name: Disable Performance
Value Type: REG_DWORD Value Data: 1



MORE INFORMATION
The AutoDiscovery/AutoPurge (ADAP) process is responsible for collecting and maintaining performance counter objects in WMI that are registered on the computer.

The ADAP process starts when the WinMgmt service is started or when performance libraries, which contain the performance counters, are installed or uninstalled using the lodctr/unlodctr utilities.

Although the above entries are logged, the counters are still available.