WMI ADAP??

Hisumi

Junior Member
Oct 9, 2000
12
0
0
Hello
Recently i've been suffering from this WMI ADAP error (event 41) on my win2k system
each time this error is a little different..(this error appears in my application log)
eg.
- WMI ADAP was unable to create object index 1848 for Performance Library RSVP because no value was found in the 009 subkey
- WMI ADAP was unable to load the perfproc.dll performance library due to an unknown problem within the library: 0x0
etc etc

i wish i can get more additional info on this type of error and how to fix it other than formatting my computer.

thnx
 

jaywallen

Golden Member
Sep 24, 2000
1,227
0
0
Hi,

Well, there are a lot of funny things going on with the Windows 2000 Performance Library. Most of the time, especially when the error messages are numerous and varied, it seems to be caused by an incompatible extensible performance counter that's been installed along with a device driver or software installation. I haven't seen this particular error on any of the systems under my purview, but I have handled similar issues by using the exctrlst.exe utility from the Windows 2000 Resource Kit to disable the offending extensible performance counters I've identified on various systems.

In performing a quick search at the JSI site I found one tip that probably applies directly to your situation. Or you might wish to just go to the main search page of the JSI, Inc. site and try out your own search terms.

It does no harm to turn off a counter, assuming that the device or function it's monitoring is actually behaving itself. Most of the performance monitor errors I've seen so far have been the result of a failure in the reporting mechanism itself, rather than a failure in the item being monitored.

I hope this helps. If you really want to pin this down, you'll probably have to roll up your sleeves. It's kind of interesting for a while, but becomes kind of boring eventually. At that point, most people I know just decide to disable the offending counters rather than try to figure out just what timeout parameter or other issue is causing them to issue the error messages.

Regards,
Jim