The user has changed the ASPNET user permission on his/her own. As a result, the entire website cannot be used. Record the information.

Server Error:

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.

You can solve this problem in the following ways:

========================================================== ==========

This articleArticleThe information in applies:

Microsoft ASP. NET (provided together with the. NET Framework)

Microsoft Internet Information Service 5.0

Microsoft mobile Internet Toolkit (mmit)

The release number of this article was chs315158.

Symptom

After Microsoft Visual Studio. NET or Microsoft. NET Framework is installed on the domain controller or backup domain controller, if you try to run an ASP. NET applicationProgram, The browser will display the following error message:

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.

In addition, the system application event log records the following events:

aspnet_wp.exe cocould not be launched because the username and/or password supplied in the processmodel section of the config file are invalid.
aspnet_wp.exe cocould not be started.
hresult for the failure: 80004005
This issue involves Internet Information Service (IIS) version 5.0 or later.
cause
by default, Asp. net uses a weak account (the local computer account named ASPnet) to run its auxiliary processes. All user accounts on the domain controller or backup domain controller are domain accounts, not local computer accounts. Because of this, aspnet_wp.exe cannot be started 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 section of the machine. config file or use the system account.

Note: If you try debugging before you try to browse the page (click the start button), the problem will be identical.

Solution

To solve this problem, use one of the following methods:

Create a weak account with the correct permissions and use the account in the <processmodel> section of the machine. config file.

In the <processmodel> section of the machine. config file, set the username attribute to system.

The <processmodel> section of the machine. config file uses the administrator account.

NOTE: If ASP. NET applications are allowed to run as system or administrator accounts, serious security problems may occur. If any work und is usedCodeYou can access the domain controller and domain settings. Executable files started from the aspnet_wp.exe process run in the same context, and they can also access the domain controller.

Therefore, Microsoft recommends the first work und. To use the first work und, perform the following steps:

Create a user account named aspuser on the computer and add the account to "user group.

Note: If you have changed the password of the ASPNET account created by the. NET Framework, you can also use this account. You must know the password of this account, because you need to add the password to the <processmodel> section in the subsequent steps.

Grant the "Log on as a batch job" user permission to the aspuser or ASPNET account. Make sure that this change is displayed in "Local Security Policy" settings.

Note: To grant this account the "Log on as a batch job" user permission, you must authorize this user permission in each of the following security policies (starting with "Control Panel"/"Administrative Tools ):

Domain Controller Security Policy

Domain Security Policy

Local Security Policy

Note: You must restart the server to make these changes take effect.

Make sure that the aspuser or ASPNET account has the permission to access all directories and files necessary to start the aspnet_wp.exe process and provide services for ASP. NET pages. For more information about which permissions must be granted to this account, click the following article number to view the article in the Microsoft Knowledge Base:

317012 info: process and request ID in ASP. NET

Open the machine. config file. The file path is % SystemRoot % \ Microsoft. NET \ framework \ v1.0.3705 \ config.

In the <processmodel> section of the machine. config file, change the username and password attributes to the name and password of the Account Created in step 1. Example: username = "domainname \ aspuser" Password = "aspuserpassword"

Save the changes made to the machine. config file.

Status

Microsoft has confirmed that this is an error in Microsoft products listed at the beginning of this article.

Reference

For more information about ASP. NET security, click the following article number to view the article in the Microsoft Knowledge Base:

306590 info: ASP. NET Security Overview

========================================================== =

^ O ^

Remember to set security attributes for the website folder. The system account is fully controlled.

Author's blog:Http://blog.csdn.net/bgu/