Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: ASP.NET does not work with the default ASPNET account on a domain controller
Article ID: 315158 - View products that this article applies to.
This article was previously published under Q315158
After you install Microsoft Visual Studio .NET or the Microsoft .NET Framework on a domain controller or on a backup domain controller, if you try to run an ASP.NET application, the browser displays the following error message:
Furthermore, the following event is logged in the system application event log:
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable.
Please hit the "Refresh" button in your web browser to retry your request.
This applies to Internet Information Services (IIS) version 5.0 or later.
aspnet_wp.exe could not be launched because the username and/or password supplied in the processModel section of the config file are invalid.
aspnet_wp.exe could not be started.
HRESULT for the failure: 80004005
By default, ASP.NET runs its worker process (Aspnet_wp.exe) with a weak account (the local machine account, which is named ASPNET) to provide a more secure environment. On a domain controller or on a backup domain controller, all user accounts are domain accounts and are not local machine accounts. Therefore, Aspnet_wp.exe fails to start because it cannot find a local account named "localmachinename\ASPNET". To provide a valid user account on the domain controller, you must specify an explicit account in the <processModel> section of the Machine.config file, or you must use the SYSTEM account.
Note If you try to debug (click the Start button) before you try to browse to the page you can experience the exact same problem.
To work around this problem, use one of the following methods:
Therefore, Microsoft recommends that you use the first workaround. To use the first workaround, follow these steps:
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This bug was corrected in ASP.NET (included with the .NET Framework) 1.1.
For more information about ASP.NET security, click the following article number to view the article in the Microsoft Knowledge Base:
306590For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/306590/ )ASP.NET security overview
(http://support.microsoft.com/kb/316989/ )Error message when you create a trusted data connection from ASP.NET to SQL Server: "Login failed for user: 'AccountName'"
(http://support.microsoft.com/kb/329290/ )How to use the ASP.NET utility to encrypt credentials and session state connection strings
(http://support.microsoft.com/kb/317012/ )Process and request identity in ASP.NET
Article ID: 315158 - Last Review: December 19, 2007 - Revision: 5.3