BUG: Performance counters may have inaccurate results when a user without permission runs the ASP.NET worker process

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: When you run Microsoft ASP.NET Web applications, you may experience unexpected results with the following counters for the ASP.NET Applications performance object:

• Anonymous requests per second
• Requests per second
• Cache API hit ratio

This problem occurs when the worker process of ASP.NET runs as a user without sufficient security permissions.

To work around this problem in Microsoft Windows Server 2003, add the user to the IIS_WPG group.

To work around this problem in Microsoft Windows XP and Microsoft Windows 2000, modify the security settings of the user who will run the ASP.NET worker process with Registry Editor:

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK to start Registry Editor.
3. Locate the following registry key:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_1.1.4322\Names
4. Right-click Names, and then click Permissions.
5. Click Advanced.
6. In the Permission entries list, click and then edit the user who will run the ASP.NET worker process. If the user in not in the Permission entries list, click Add, and then add the user.
7. In the Apply onto list, click This key only, and then click to select the Allow check boxes that are next to the following terms:
   • Query Value
   • Set Value
   • Create Subkey
   • Enumerate Subkeys
   • Notify
   • Read Control
8. Click OK, and then quit Registry Editor.

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

To reproduce this problem, create a user with the default permission values. Use that user to run the ASP.NET worker process.