C:\Windows\Microsoft.NET\Framework\V4.0.30319\aspnet_regiis-i
Note: C:\Windows\Microsoft.NET\Framework\V4.0.30319\ is the corresponding path of netframework installation;
If it is a 64-bit server, you need to go to C:\Windows\Microsoft.NET\Framework64\v4.0.30319 for installation ~!
In this way, you can generally resolve this error:
Errore HTTP 404.2-not Found "The content requested by IIS 7.5 appears to be a script and therefore cannot be handled by a static file handler
3), ISAPI and CGI limitations issues
This error occurs because asp.net4.0 support is not enabled in the ISAPI and CGI restrictions after installing asp.net4.0.
Verbose error: HTTP error 404.2-not Found. The page you requested cannot be supplied because of the ISAPI and CGI Restrictions list settings on the WEB server.
Appearance environment: Win7 + IIS7.0
Workaround: The IIS root node-> the right "ISAPI and CGI restrictions"-> to set the prohibited Dotnet version entry to allow.
4), default page settings:
Site deployment and IIS6 are similar. Setting the default page is not the same as IIS6.
1. In the functional view, IIS-> the default document
2. Point add, enter your page (how to folder, also to enter together).
3. Then, right click on your page and click Enable.
Note: If you delete this default page in the file system, IIS7 will also delete your settings in the default document!
5), HTTP error 500.19-internal Server error Error
1, IIS and VS installation sequence caused the problem.
Solution: If you install IIS after VS, simply re-register the ASPNET, as follows
1 open to run, enter cmd into the command Prompt window.
2 into the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 directory.
3 input Aspnet_regiis.exe–i execution can be noted: if the system is a 64-bit second step path for C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727
2, net2.0 version of the program appears this error.
Workaround:
HTTP Error 500.22-internal Server error may also be reported
Detects asp.net settings that are not applicable in integrated managed piping mode.
Turn on IIS, select the basic settings in the right operation, click Next to the application pool, choose
Classic. NET AppPool, and switch the admin mode to Classic mode OK.
3, the issue of permissions caused.
The original folder, right-click to select its properties, open the Security tab, see "Group or User name", click the Edit button to add a new username "Everyone", and then change its permissions, and set the second permission "modify" to allow
The problem I've encountered is due to permission problems. Win7 has a higher level of privilege.
If your files are on the desktop, you need to set everyone's read and write permissions.
