Symptoms
Consider the following scenario:
-
You have installed Microsoft .NET Framework 3.5 Service Pack 1 (SP1).
-
You use System Monitor (PerfMon) to monitor the performance of running ASP.NET applications.
In this situation, you may notice that the performance counter "ASP.NET Apps v2.0.50727(__Total__)\Sessions Active" sometimes shows an unreasonably high value. For example, the value that is shown is 4294967267.
Note The Sessions Active counter indicates the number of sessions currently active. For more information about how to monitor ASP.NET applications by using PerfMon, see the "More information" section.
Resolution
Hotfix Replacement Information
The hotfix that corresponds to KB969722 has been superseded with the hotfix KB981201, which contains all fixes that were previously included in KB969722 . You should use the hotfix KB981201 to fix the issues described in KB969722. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981201 A hotfix is available for ASP.NET 2.0 that enables support for extended protection
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about ASP.NET Performance Monitoring, visit the following Microsoft web site:
Using the System Monitor (PerfMon) with ASP.NET applicationshttp://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/b4d4d195-2ecb-4728-9348-6f1bfa1a1b63.mspx?mfr=true
System and Application Performance Counters for ASP.NEThttp://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/852720c8-7589-49c3-a9d1-73fdfc9126f0.mspx?mfr=trueIn some cases, after you install this fix, when you try to access the ASP.NET Performance counters by using Windows Management Instrumentation (WMI), the counters may have values of 0. Or, there may be no counter instances listed.
For example, this issue may occur when you try to access the ASP.NET Performance counters by starting PERFMON with the /WMI switch or by using Microsoft Operations Manager (MOM) or Systems Center Operations Manager (SCOM).
Microsoft are still investigating this issue. However, you can use the following procedure to workaround this issue:
-
Open Wbemtest.exe
-
Connect to the root\cimv2 namespace.
-
Delete the Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 class.
-
Winmgmt /resyncperf
-
Net stop winmgmt
-
Net start winmgmt
For more information, see the following MSDN blog post:
