This website is supported, hosted and funded by Corelan Consulting - https://www.corelan-consulting.com. Please follow us on Facebook (@corelanconsulting) and Twitter (@corelanconsult). Corelan training schedules: https://www.corelan-training.com/index.php/training-schedules



Please consider donating: https://www.corelan.be/index.php/donate/


7,829 views

WMI ADAP was unable to create the object Win32_PerfRawData_ ASPNET_2050727_ASPNETAppsv2050727

Scenario : OpsMgr SP1 (RC, but problem also exists in the RTM version) on Windows Server 2003 SP2 fully patched, OpsMgr agents deployed to various servers.

Soon after deploying the agents, I started getting the following error message on various servers :

WMI ADAP was unable to create the object Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 for Performance Library ASP.NET_2.0.50727 because error 0x80041001 was returned

The Application event logs reported these (or similar) events :

Event ID 35
Source : WinMgmt
Category : None
Type : Warning
WMI ADAP was unable to load the ASP.NET_2.0.50727 performance library because it returned invalid data: 0x0

Event ID 40
Source : WinMgmt
Category : None
Type : Warning
WMI ADAP was unable to create the object Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 for Performance Library ASP.NET_2.0.50727 because error 0x80041001 was returned

 

I filed a bug report to Microsoft regarding this issue (in februari 2008, see http://connect.microsoft.com/OpsMgrFeedback/feedback/ViewFeedback.aspx?FeedbackID=328738). Other people indicated that they could reproduce the bug, and Microsoft was able to reproduce the bug and determined that this was caused by certain .Net framework updates.   So far so good.

Finally, they closed the issue, telling me to contact CSS to get the fix. Even better.

Today, they have finally created an official KB article for this bug.

This Microsoft KB article that explains how to fix this can be found at http://support.microsoft.com/kb/951683/en-us

Also, have a look at http://mcpguides.com/?p=38, which explains how to set up a workaround for this (basically, it explains how to disable the performance counters for ASP.Net). If you want to fix this problem as opposed to bypass the problem, you will either have to contact CSS (http://support.microsoft.com/contactus/?ws=support) or visit this hotfix page in order to get the fix.

 

Glad to see this is solved (after 7 months).

© 2008 – 2015, Corelan Team (corelanc0d3r). All rights reserved.

Related Posts:

  • No Related Posts

Comments are closed.

Corelan Training

We have been teaching our win32 exploit dev classes at various security cons and private companies & organizations since 2011

Check out our schedules page here and sign up for one of our classes now!

Donate

Want to support the Corelan Team community ? Click here to go to our donations page.

Want to donate BTC to Corelan Team?



Your donation will help funding server hosting.

Corelan Team Merchandise

You can support Corelan Team by donating or purchasing items from the official Corelan Team merchandising store.

Protected by Copyscape Web Plagiarism Tool

Corelan on Slack

You can chat with us and our friends on our Slack workspace:

  • Go to our facebook page
  • Browse through the posts and find the invite to Slack
  • Use the invite to access our Slack workspace
  • Categories