Re: WMI Win32_PerfFormattedData hosed - how to fix?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I realize you are probably working on this in your spare time, so I don't wish to push. :)

However, I was curious if you were able to find out anything further on this issue?

Thanks in advance for your time.

Later,
Chris

Manbinder Pal Singh [MSFT] wrote:
Starting with ContentFilter library all the subsequent libraries failed and PerfOS and PerfNet being one of those and so you dont get the data what you want.



Only which passed were

.NET CLR Data performance

.NET CLR Networking

.NET Data Provider for Oracle

.NET Data Provider for SqlServer

.NETFramework

ASP.NET libraries

aspnet_state



VerifyLoaded fails for all the failing libraries and subsequent failures may be because of that

Constructing the PerfOS performance library wrapper.

(Mon Jan 22 16:26:25 2007.70788859) : VerifyLoaded for PerfOS hr = 80041001.

(Mon Jan 22 16:26:25 2007.70788859) : Construction of the PerfOS perflib wrapper failed hr = 80041001.

(Mon Jan 22 16:26:25 2007.70788859) : CAdapPerfLib::EndProcessingStatus()...

(Mon Jan 22 16:26:25 2007.70788859) : Destructing the PerfOS performance library wrapper.

(Mon Jan 22 16:26:25 2007.70788859) : CPerfLibSchema::Initialize for PerfOS hr 80041001

(Mon Jan 22 16:26:25 2007.70788859) : ProcessLibrary ForceStatus for PerfOS hr = 80041001

(Mon Jan 22 16:26:25 2007.70788859) : ProcessLibrary ForceStatus for PerfOS hr = 80041001





Let me dig more as when it can fail with 80041001. Thank for your patient.




Thanks,
Manbinder Pal Singh

This posting is provided "AS IS" with no warranties, and confers no rights.


"Manbinder Pal Singh [MSFT]" <manbins@xxxxxxxxxxxxx> wrote in message news:eEbpD93PHHA.1280@xxxxxxxxxxxxxxxxxxxxxxx
Yes I got them now and i jsut had a first glance it. Your log suggests that the adap process failed for some libraries. I will try to see and dig further deep sometime and let you know.

Thanks,
Manbinder Pal Singh

This posting is provided "AS IS" with no warranties, and confers no rights.

"Chris Richards" <gizmo@xxxxxxxxxxxxx> wrote in message news:%23i23aJyPHHA.856@xxxxxxxxxxxxxxxxxxxxxxx
I e-mailed them shortly after my previous post. Have you not received them yet?
Later,
Chris

Manbinder Pal Singh [MSFT] wrote:
OK. Logs please?


Thanks,
Manbinder Pal Singh

This posting is provided "AS IS" with no warranties, and confers no rights.


"Chris Richards" <gizmo@xxxxxxxxxxxxx> wrote in message news:Oyoo9UnPHHA.4156@xxxxxxxxxxxxxxxxxxxxxxx
Thank you.
I have tried the items mentioned below with no success. I am sending you the logs as requested.

Later,
Chris

Manbinder Pal Singh [MSFT] wrote:
I would recommend you to try again the following steps.
1. Clean all logs ( delete all ) and event log after taking backup in case you need it laters.
2. net stop winmgmt and net start winmgmt
3. see if the above two fixes your problem
4. Otherwise try each operatino below one by one and see the logs and the event log and tell if there is any winmgmt or ADAP message.
5. winmgmt /clearadap
6. winmgmt /resyncperf

Send the wmiadap.log , winmgmt log and if any events are there in event log.

Thanks,
Manbinder Pal Singh

This posting is provided "AS IS" with no warranties, and confers no rights.


"Chris Richards" <gizmo@xxxxxxxxxxxxx> wrote in message news:eLp%23D3cPHHA.2340@xxxxxxxxxxxxxxxxxxxxxxx
Well, reinstalling the service pack didn't fix it either.

I guess I'm going to have to break down and spend $200 to call Microsoft. :(

Later,
Chris

Chris Richards wrote:
Yes, I did try rerunning the commands. I haven't tried reinstalling the service pack. I'll give that a shot.

Thanks

Later,
Chris

joseomjr@xxxxxxxxx wrote:
After you re-registered did you try running those commands? Maybe try
re-installing the service pack?


Chris Richards wrote:
Ok, maybe we are attacking this problem from the wrong end.

It doesn't look like ANY of the classes that are provided via
wbemperf.dll or wmicookr.dll are in the registry.

I've done:

regsvr32 wbemperf.dll

and

regsvr32 wmicookr.dll

and both commands completed successfully.

So, any ideas on what could be allowing the DLLs to successfully
register, yet prevent the class information from properly registering?

BTW, thanks for all your help so far.

Later,
Chris

joseomjr@xxxxxxxxx wrote:
You can always try deleting the repository data which WMI will rebuild
on its own from the MOF files.

C:\WINDOWS\system32\wbem\Repository\FS

Chris Richards wrote:
I've been working on an ATL client to talk to WMI.

In the course of working on this, I was investigating the
Win32_PerfFormattedData_PerfOS_Processor class and had started getting
some data under the debugger when I lost power.

When I came back up, my WindowsXP machine appeared to come up clean
(didn't try to run chkdsk on the way up) but just to be sure I manually
ran chkdisk to check for problems. None were reported.

Since the crash, I haven't been able to get data on
Win32_PerfFormattedData_PerfOS_Processor,
Win32_PerfRawData_PerfOS_Processor, or indeed any of about 24 total
classes in these same families. WMIDiag reports an error 0x80041010
enumerating these classes. I have tried repairing the WMI registry by
following the instructions listed at
http://windowsxp.mvps.org/repairwmi.htm but have had no luck. All of
the classes that are giving me problems appear to belong to wmicookr.dll
(which exists in %systemroot%\system32\wbem and which I have
re-registered) and are enumerated in WMI.MOF (which also exists, and
which I have also re-registered).

I'm at a complete loss here, and I do NOT want to have to reinstall this
entire machine just so I can fix this.

One other observation is that I have a little program which enumerates
the performance registry keys in the Performance Registry Interface.

Prior to this crash, I had a whole huge list of keys. Since this crash,
I have many fewer keys, and the last key enumerated appears to only be
partially there.

Any help, ideas, suggestions, pointers? I've been fighting with this
for two days. This does not seem to be a unique problem either. I've
seen numerous references to the 0x80041010 error, or 0x80041002, which
I've also seen, without any successful resolutions.

Thanks in advance



.

Relevant Pages