Recently, some readers came across a famous error message that said wmi adap could not create a win32 object. This problem can arise for several reasons. Let’s discuss some of them below.
This website is intended to be maintained, hosted and funded by Corelan von Consulting – https://www.corelan-consulting.com. Please follow us on Facebook (@corelanconsulting) and Twitter (@corelanconsult). Corelan Training Plans: https://www.corelan-training.com/index.php/training-schedules
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
1. Download Fortect and install it on your computer
2. Launch the program and click "Scan"
3. Click "Repair" to fix any issues that are found
Scenario: OpsMgr SP1 (RC, but there is a problem in the RTM version as well) on Windows Server 2003 SP2 is fixed in general, OpsMgr agents are deployed on assortment servers.
Shortly after deploying the agents, I received the following error on different hosts:
WMI ADAP could not create Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 object for ASP.NET_2.0.50727 performance library because it returned error 0x80041001
Event ID 25 Source: WinMgmt Category: None Type: Warning WMI ADAP could not load the ASP.NET_2.0.50727 performance library because it returned information and invalid facts: 0x0
Event ID 40 Source: WinMgmt Category: None Type: Warning WMI ADAP could not create Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 object for ASP.NET_2.0.50727 library performance, so k he returned error 0x80041001 / p>
I reported a bug to Microsoft related to this issue (see http://connect.microsoft.com/OpsMgrFeedback/feedback/ViewFeedback.aspx?FeedbackID=328738 for details in February 2008). Other people have stated that they were able to reproduce the bug, and that Microsoft was able to reproduce the bug, and that the bug has identified the cause of some .Net layout updates.
Finally, we closed our issue and asked me to contact CSS Time for a solution. Even better.
Today, many people have finally created an official article about this KB / s error.
Also see http://mcpguides.com/?p=38 for how to add a workaround for this (below explains how to disable performance counters for ASP.Net). … If you want to run this issue instead of working on a solution, you either need to add your personal CSS Aria-hidden = “true”> http: // support () or visit this hotfix page for this solution.
