Workaround for HTTP error 500.19 Internal Server error

The first possibility is to solve some of the problems

Http://wenku.baidu.com/view/c5cb4a08bb68a98271fefa3f.html

second possibility , solve another part of the problem

After the inspection was found because the installation of vs2008 after the installation of IIS, just re-register under the ASPNET can be, the steps are as follows

1 Open run, enter cmd into the command Prompt window.

2 enter into the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 directory.

3 input aspnet_regiis.exe–i execution can be

Note: If the system is a 64-bit path to the second step of C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727

The third possible solution : Win7 The problems I have encountered

WIN7. NET development encountered another problem: HTTP error 500.19-internal Server error, unable to access the requested page because the page's related configuration data is invalid.

Verbose error message module IIS WEB Core

Notify BeginRequest

Handler not yet determined

Error code 0x80070021

Configuration errors cannot use this configuration section in this path. This behavior occurs if the section is locked at the parent level. The lock is set by default (overridemodedefault= "Deny"), or is explicitly set by a location tag that contains overridemode= "deny" or the old allowoverride= "false".

Configuration source

219:

220:

221:

Workaround:

Control Panel--programs and features--turn Windows features on or off--role

Here, if you have not yet installed Web server (IIS), select Add.

If it is already installed, select Web Server (IIS) and add the role service.

Select "Application Development (installed)" and "ASP."

Other similar error one: [This Part I did not test, skip directly, see below]

HTTP Error 500.19-internal Server error
Configuration error: This configuration section cannot be used in this path. This behavior occurs if the section is locked at the parent level. The lock is set by default (overridemodedefault= "Deny"), or is explicitly set by a location tag that contains overridemode= "deny" or the old allowoverride= "false".

This error occurs because IIS 7 employs a more secure Web. config management mechanism, which by default locks the configuration items from being allowed to change. To unlock you can run the command line

%windir%\system32\inetsrv\appcmd unlock Config-section:system.webserver/handlers [This is the line, help me fix it!] ]。

The handlers is the name of the node in the error message that is displayed in red characters.

If modules is also locked, you can run%windir%\system32\inetsrv\appcmd unlock config-section:system.webserver/modules

Also, if you are using an ASP. NET friend, when installing IIS7, please check the ASP. NET, the default is not selected, there will be similar error message

Other similar error two:

HTTP Error 500.19-internal Server error
The requested page cannot be accessed because the associated configuration data for the page is invalid.

Verbose error message module IIS WEB Core
Notify BeginRequest
Handler not yet determined
Error code 0x80070005
Configuration error Unable to read configuration file due to insufficient permissions

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 user name "Everyone", then change its permissions, set the second permission "modify" to allow it. : [I didn't try that either]

Source http://www.veryhuo.com/a/view/20835.html

Http://techrich.cnblogs.com

I passed the first---------and the third method, the successful transition from the original error to the

HTTP Error 500.21-internal Server error handler "ScriptHandlerFactory" has an error module in its module list "Managedpipelinehandler" Verbose error message module IIS Web Core notification Executerequesthandler Handler scripthandlerfactory error code 0x8007000d request urlhttp://localhost:5001/ Passportservice.asmx Physical path E:\XXXXXXXX (encrypted here) \passportservice.asmx logon method Anonymous Logon user anonymous the most likely cause:

• Managed handlers are used, but ASP. NET is not installed or fully installed.
• There is a typographical error in the configuration of the handler module list.

Actions you can try:

• If you want to use a managed handler, install ASP.
• Make sure that the name of the handler module is specified correctly. The module name is case-sensitive and uses the modules= "Staticfilemodule,defaultdocumentmodule,directorylistingmodule" format.

Links and more information the IIS kernel does not recognize this module.

See more information?

4. Then, looking again on the network, finally, the cmd command was used:

C:\Windows\Microsoft.NET\Framework
More sources: http://www.zgjx114.com
\v2.0.50727>aspnet_regiis.exe-i
Start installation of ASP. NET (2.0.50727).
................................................................................
.
ASP. NET (2.0.50727) installation is complete.

Start ok! again

Workaround for HTTP error 500.19 Internal Server error