Sunday, September 5, 2010

Resolving ASP Performance Counter Application Event Log Warnings

Tagged with: , , ,
Friday, May 23, 2008, 21:44
This news item was posted in SCOM 2007, Windows Server category and has 9 Comments so far.

After the installation of System Center Operations Manager 2007 SP1 RTM, you may notice the occurrence of several warnings in the Application event log on Agent-managed servers related to 32 bit ASP.Net performance counters, 64 bit ASP.Net performance counters, or both depending on the configuration of your system. The warnings are as follows:

Event ID: 35
Source: WinMgmt
Description: WMI ADAP was unable to load the ASP.NET_64_2.0.50727 performance library because it returned invalid data: 0×0

Event ID: 35
Source: WinMgmt
Description: WMI ADAP was unable to load the ASP.NET_64 performance library because it returned invalid data: 0×0

Event ID: 40
Source: WinMgmt
Description: WMI ADAP was unable to create the object Win32_PerfRawData_ASPNET_64_2050727_ASPNETAppsv2050727 for Performance Library ASP.NET_64_2.0.50727 because error 0×80041001 was returned

Event ID: 40
Source: WinMgmt
Description: WMI ADAP was unable to create the object Win32_PerfRawData_ASPNET_64_ASPNETApplications for Performance Library ASP.NET_64 because error 0×80041001 was returned

More details of this issue can be found here:

http://connect.microsoft.com/OpsMgrFeedback/feedback/ViewFeedback.aspx?FeedbackID=328738

These events can occur frequently, and depending on the number of agents and your configuration can become quite bothersome in large environments. The errors are related to a known MS Bug having to do with WMI attempts to query the ASP.Net performance counters, for which no hot fix currently exists. Assuming that on the agent managed host you have no additional needs outside of System Center to monitor the ASP.Net performance counters there are two ways to rid yourself of these errors:

1: Download the Windows 2000 Resource Kit tool "Extensible Performance Counter List" (exctrlst.exe) here: http://www.microsoft.com/downloads/details.aspx?familyid=7ff99683-b7ec-4da6-92ab-793193604ba4&displaylang=en

Install and launch the tool, once you have it open, uncheck the "Performance Counters Enabled" check box for all versions of ASP.Net that you have installed.

exctrlst.exe

2: If you have large environments and installing the tool on each impacted machine is not a realistic option, you can script the registry key that exctrlst.exe is modifying. The net impact of setting the "Performance Counters Enabled" checkbox is that the DWORD Value of "Disable Performance Counters" is set to 1. This DWORD can be located at:
HKLM\SYSTEM\CurrentControlSet\Services\%Insert ASP.net node%\Performance

registry

Note: In some instances this key does not exist and must be created.

Once these changes have been implemented you should see a clean event Application Event log on the impacted server.

You can leave a response, or trackback from your own site.

9 Responses to “Resolving ASP Performance Counter Application Event Log Warnings”

  1. ulrich bernskov said on Thursday, July 3, 2008, 18:10

    Thanks for the descriptive solution.
    Please post a follow-up should a solution be provided

  2. michel said on Thursday, July 17, 2008, 6:45

    Be aware. What you now doning is DISABLELING all dot net performance counters !!!! So applications (as SCOM) may not be able to work correctly. This is not a solution but a high impact workarround.

  3. ulrich bernskov said on Thursday, July 17, 2008, 13:28

    Hi michel.
    Do you have a better idea?

  4. MCPGuides.com said on Thursday, July 17, 2008, 18:17

    Michel,

    You are correct. We are clearly disabling the ASP.Net performance counters, this is why we've given the warning that "Assuming that on the agent managed host you have no additional needs outside of System Center to monitor the ASP.Net performance counters there are two ways to rid yourself of these errors:"

    Doing so has no impact on the functionality of SCOM, or other applications, outside of simply being unable to monitor and collect ASP.Net performance metrics, which is clearly not possible on hosts impacted by this bug as it is.

    Since we are already unable to collect ASP.Net performance on machines impacted by this bug, what we are doing is cleaning up the noise in the event log until such time that a proper hotfix from Microsoft becomes available.

  5. michel said on Thursday, July 17, 2008, 18:27

    Hi,

    You have only to disbale the "ASP64 application" counters. The other ASP 64 is working good. (you can check this with perfmon) So some MP workflows will maybe work. I agree with you that if you are sure that no dot net 2.0 applications are running and needs to be monitord that it is no problem to disbale this perf lib. But don't forget that you have done this.

    Is there any more info on this hoffix where everybody talks about ?

  6. MCPGuides.com said on Thursday, July 17, 2008, 18:43

    Michel,

    According to the Microsoft engineers we have spoken with no hotfix is in development at this time for this bug. If your business is being seriously impacted by this issue you can open up a QFE request with them.

    The general discussion about a hotfix seems to be more related to the desire for MS to create a hotfix for this, rather than the actual existence of a hotfix.

  7. michel said on Friday, July 18, 2008, 8:56

    Hi,

    Good news. I've spoken to our internal microsoft engineer and there is a non-public hotfix for this. See KB951683. The public release is inplemented in Dot net 3.5 Sp1.

    I've already inplemented this non-public hotfix and it WORKS!! So all the dot net 2.0 counters are working now.

    Hope this helps a lot off people.

    See link for some more info: http://blogs.msdn.com/carloc/archive/2008/06/04/wmi-warnings-35-and-40-with-asp-net.aspx

    Michel Kamp

  8. anonymous said on Monday, August 18, 2008, 10:21

    For those who don't/can't install .NET 3.5 SP1 or for Windows 2000-based computers, go to this link (http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=951683&kbln=en-us) and obtain the hotfix.

  9. WMI ADAP was unable to create the object Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 | Peter Van Eeckhoutte's Blog said on Tuesday, September 16, 2008, 23:16

    [...] 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 [...]

Leave a Reply