SYMPTOMS
When you try to browse to pages in an ASP.NET application, you cannot open them, and you receive the following error message in the browser:
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.
Administrator Note: An error message detailing the cause of this specific request failure can be found in the system event log of the web server. Please review this log entry to discover what caused this error to occur.
The following error is also logged in the Application event log:
aspnet_wp.exe could not be started. HRESULT for the failure: 80004005
CAUSE
This problem occurs if the name of the computer that is hosting the ASP.NET Web application contains any of the following words at the beginning, the middle, or the end of the computer name:
- SYSTEM
- ADMINISTRATORS
- INTERACTIVE
RESOLUTION
To work around this problem, use one of the following methods.
Workaround 1
Do not use a computer name that contains "SYSTEM," "ADMINISTRATORS," or "INTERACTIVE." You can change the computer name of the server.
For additional information about steps to take if you change the computer name, click the article number below
to view the article in the Microsoft Knowledge Base:
234142 Updating IIS After You Change the Computer Name
NOTE: If you change a computer name, you may notice unintended side effects. If this occurs, reload the computer, and then specify a new computer name.
Workaround 2
Set the identity of the ASP.NET worker process (Aspnet_wp.exe) to the SYSTEM account or to an Administrator account.
For additional information about how to do this, click the article number below
to view the article in the Microsoft Knowledge Base:
317012 INFO: Process and Request Identity in ASP.NET
NOTE: Microsoft does not recommend that you set the ASP.NET worker process to run as the SYSTEM account or as an Administrator account. If malicious code is somehow executed under ASP.NET, that code can do more damage if the code runs under a highly privileged account such as the SYSTEM account or an Administrator account.