|
 |
 |
 |
|
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 918041 - Last Review: December 7, 2007 - Revision: 3.3 An IIS 6.0 application pool may unexpectedly exit when a worker process shuts down or is recycledConsider the following scenario. You set up a Microsoft Internet Information Services (IIS) 6.0 application pool. The application pool contains a Microsoft ASP.NET 2.0 application. A worker process in the application pool shuts down or is recycled. In this scenario, the application pool may unexpectedly exit. This problem occurs because a worker process in an application pool does not have sufficient permissions to access and write to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<ASP.NETVersion>\Names represents the version of ASP.NET that is installed. To work around this problem, follow these steps: - Add the application pool identity user account to the IIS_WPG group. (By default, the NETWORK SERVICE user account is the application pool identity user account.) To do this, follow these steps:
- Click Start, right-click My Computer, and then click Manage.
- Expand Local Users and Groups, and then click Groups.
- Right-click IIS_WPG, and then click Properties.
- In the IIS_WPG Properties dialog box, click Add.
- In the Select Users, Computers or Groups dialog box, click Advanced.
- Click Find Now.
- In the Search results pane, click the application pool identity user account, and then click OK.
- Click OK.
Note All the application pool identities should be members of the IIS_WPG group. - Make sure that the IIS_WPG group has the necessary permissions to access the ASP.NET Names registry entry. To grant IIS_WPG the necessary permissions, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_2.0.50727\Names - Right-click Names, and then click Permissions.
- Click Add, type IIS_WPG, click Check Names, and then click OK.
- In the Permissions for Names dialog box, click Advanced.
- In the Advanced Security Settings for Names dialog box, click the Permissions tab, click IIS_WPG, and then click Edit.
- In the Permission Entry for Names dialog box, make sure that IIS_WPG is in the Name box.
- Click to select the following check boxes:
- Query Value
- Set Value
- Create Subkey
- Enumerate Subkeys
- Notify
- Read Control
- In all the dialog boxes, click OK, and then exit Registry Editor.
Note If the server is a domain controller, you must change the application pool identity to a new domain user account or to an existing domain user account. To do this, follow these steps: - Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
- In IIS Manager, expand the server, expand Application Pools, right-click the name of the application pool that you want to modify, and then click Properties.
- In the Application_Pool Properties dialog box, click the Identity tab.
- Click Configurable, type the account user name. Or, click Browse to locate the account.
- Type the account password in the Password box, and then click OK.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. For more information about how to configure the application pool identity in IIS 6.0, visit the following Microsoft Web site:
For more information about the NETWORK SERVICE account, the IIS_WPG group, and other IIS 6.0 built-in accounts, visit the following Microsoft Web site:
APPLIES TO- Microsoft ASP.NET 2.0
- Microsoft Internet Information Services 6.0
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
|
 |
|
 |
|
|
|
| |