How to solve the 500.19 and 500.21 errors reported by win7_iis

How to solve the 500.19 and 500.21 errors reported by win7_iis

HTTP Error 500.19 internal server error Solution

Another problem encountered during. NET development under win7: HTTP Error 500.19-internal server error. The requested page cannot be accessed because the configuration data on this page is invalid.

Detailed error information module IIS Web Core
Notification beginrequest
The handler has not been determined
Error code 0x80070021
Configuration error cannot be used in this path. This situation occurs if this section is locked at the parent level. The lock is set by default.
(Overridemodedefault = "deny"), or by specifying the location that contains overridemode = "deny" or the old AllowOverride = "false"
Set.

Configuration Source

219: <Add name = "scriptmodule" precondition = "managedhandler" type = "system. Web. Handlers. scriptmodule,
System. Web. Extensions, version = 3.5.0.0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/> </modules>
220: 221: <remove name = "webservicehandlerfactory-integrated"/>
Solution:
<! -- [Endif] -->
Control Panel --> Programs and functions --> enable or disable Windows functions --> roles
If "Web Server (IIS)" is not installed yet, select "add ".
If it is already installed, select "Web Server (IIS)" --> Add role service.
Select "Application Development (installed)" --> "ASP. NET ".

Other similar errors 1:
HTTP Error 500.19-Internal Server Error
Configuration error: you cannot use this configuration section in this path. This situation occurs if this section is locked at the parent level. The lock is set by default.
(Overridemodedefault = "deny"), or by specifying the location that contains overridemode = "deny" or the old AllowOverride = "false"
Set.

This error occurs because IIS 7 adopts a safer web. Config Management Mechanism. By default, the configuration items are locked and cannot be changed. You can cancel the lock.

Run Command Line % WINDIR % \ system32 \ inetsrv \ appcmd unlock config-Section: system. webserver/handlers. The
Handlers is the node name displayed in the red letter in the error message.

If modules is also locked, run % WINDIR % \ system32 \ inetsrv \ appcmd unlock config-Section: system. webserver/modules.
In addition, if you are a friend of Asp.net, remember to check Asp.net when installing iis7. This option is not selected by default, and a similar error message will appear.

Other similar errors 2:
HTTP 500.19-Internal Server Error
The requested page cannot be accessed because the configuration data of the page is invalid.

Detailed error information module IIS Web Core
Notification beginrequest
The handler has not been determined
Error code 0x80070005
Configuration error Unable to read the configuration file due to insufficient Permissions
In the original folder, right-click its attributes, open the "Security" tab, View "group or user name", and click "edit" to add a new user name.
"Everyone", and then change its permissions. Set "modify" to allow the second permission.
Source: http://techrich.cnblogs.com

When configuring the Asp.net MVC website in IIS6
HTTP Error 500.21-Internal Server Error Solution

HTTP 500.21-Internal Server Error
The handler "pagehandlerfactory-integrated" has an error module "managedpipelinehandler" in its module list"
Cause of error: IIS6 is installed after frameworkv4.0, so that the framework is not fully installed.

Solution: you only need to re-install the program. You can re-run the program in the frameworv4.0 directory as an administrator.

% Windir % \ Microsoft. NET \ framework \ v4.0.30319 \ aspnet_regiis.exe-I

Reference: http://blog626.blog.163.com/blog/static/105610732201051591450870/