Many developers are troublesome about IIS and ASPNET installations. Here, we will do the following small summary, please exchange! IIS bad fix method !!!!!!! General IIS can't run asp.net, try the following four Method, 99% is effective: 1. The order of .NET installation should be first IIS, then install VS.NET, if the order is counternamed, or IIS is reloaded, you need to use ASPNET_REGIIS.EXE -I to reinstall IIS Mapping (mainly for ASPX, ASMX and other files) EXTENTION matches). In the C: /Windows / Microsoft.Net/framework/v1.0.3705 directory, run the lower command: aspnet_regiis.exe -i 2. Reset the ASPNET password, then find the Machine.config file in the directory below:% systemroot% / microsoft.net / framework / v1.0.3705 / config (SystemRoot is your installation directory), add / add / Modify: UserName and Password3. If it is not yet, reload IIS, then follow the method 1 to operate 4. If your machine is a domain controller, you can refer to Q315158: ASP.NET Does Not Work WitHaspnet Account on Domain Controller: http://support.microsoft.com/default.aspx? Scid = kb; EN-US; Q315158 & and You roughly talk about the steps: 1. A user named ASPUSER is created in Administrative Tools-> Active Directory Users and Computes, which is added to the user group (in User Group by default) 2. In Administrative Tools-> Local Policy-> Userright Assignment, double-click the Log on AS A Batch Job item in the right column. In the pop-up window, click Add, select or enter the ASPUSER account that just created, determine. (Restart the machine) 3. Make sure the ASPUSER account has a corresponding file, the directory access is 4. Find the Machine.config file in the directory:% systemroot% / microsoft.net/framework/v1.0.3705/config (Systemroot is your installation directory), add / modify in the
Transfer from: Dynamic Network Production Guide www.knowsky.com
