After you install the Microsoft .NET Framework 3.5 or the Microsoft .NET Framework 2.0 Service Pack 1 on a computer that is running Windows Server 2003 or Windows XP, you may experience one or more of the following symptoms:

Symptom 1

When you query some ASP.NET-related objects by using Windows Management Instrumentation (WMI), no values are returned. For example, no values are returned when you query one of the following objects:

• Win32_PerfRawData_ASPNET_ASPNET
• Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727
• Win32_PerfRawData_ASPNET_ASPNETApplications

Symptom 2

If you run the Perfmon.exe command together with the /wmi option, no ASP.NET 2.0 performance counters are listed. However, if you run the command without the /wmi option, the following counters are listed:

• ASP.NET Applications/Cache % Machine Memory Limit
• ASP.NET Applications/Cache % Process Memory Limit

Symptom 3

If you run the winmgmt /resyncperf command to register the system performance libraries by using WMI, you receive the following ASP.NET-related Warning event messages:

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

Event Type: Warning
Event Source: WinMgmt
Event ID: 40
Description:
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

Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 35
User: N/A
Description:
WMI ADAP was unable to load the ASP.NET performance library because it returned invalid data: 0x0

Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 40
User: N/A
Description:
WMI ADAP was unable to create the object Win32_PerfRawData_ASPNET_ASPNETApplications for Performance Library ASP.NET because error 0x80041001 was returned

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 3.5 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

No prerequisites are required.

Restart requirement

If the Aspnet_perf.dll file is being used when you apply the hotfix, you must restart the computer and then update the WMI performance counter classes.

Post-installation instructions

If you do not restart the computer after you apply the hotfix, follow these steps.

Note If you do restart the computer after you apply this hotfix, perform only step 2.

1. Restart the WMI service. To do this, run the following command:
   net stop "Windows Management Instrumentation"
   net start "Windows Management Instrumentation"
2. Update the WMI performance counter classes. To do this, run the following command:
   winmgmt /resyncperf

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

The .NET Framework 2.0, x86-based versions

The .NET Framework 2.0, Itanium-architecture versions

The .NET Framework 2.0, x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about the perfmon.exe /wmi command, visit the following Microsoft TechNet Web site:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: