Resolves a workaround for an ASP. NET setting that is not applicable in integrated managed pipeline mode (not simply set to Classic mode). -Catcherx

We ported the ASP. IIS6 to IIS7, which may be run with the following error:

HTTP Error 500.23-internal Server error

An ASP. NET setting was detected that is not applicable in integrated managed pipeline mode.

Why does the above error occur?

There are two modes of application pool in IIS7, one is "Integrated mode" and one is "Classic mode".

Classic mode is the way we used to be in IIS 6.

If you are using Integrated mode, you will need to change the configuration files for your custom httpmodules and httphandlers to transfer them to <modules> and

Two workarounds:

The first method, configure the application pool

Configure the application pool on IIS7 and change the schema of the program pool to "classic", after which everything is fine.

In the search engine input above the error message, the search results are almost directly changed to "classic" then a little.

But this is only expedient, with iis7.x, but actually only played 6 of the function, in addition, in some ASP. NET MVC program is not good, so we try the following workaround:

The second method, modify the Web. config configuration file:

For example, the original setting (you may not have a httpmodules,httphandlers node in your environment)

<system.web> ..... <httpmodules> <add name= "MyModule" type= " Myapp.mymodule "/> </httpmodules> <httphandlers> <add path=  "*.myh" verb= "GET" type=  "Myapp.myhandler"/> </httphandlers> </SYSTEM.WEB>           

When the IIS7 application pool is "Integrated mode", change to:

<System.web> ......</System.web><System.webserver><modules> <add name= "MyModule" type= "Myapp.mymodule"/> </modules> <handlers> span class= "tag" ><add name= "MyHandler" path= "*.myh" verb= "GET" type= "Myapp.myhandler" precondition=  "Integratedmode"/> </handlers> </SYSTEM.WEBSERVER>          

(if your web. config does not have a httpmodules,httphandlers node, add it directly in node system.webserver:

<validateintegratedmodeconfiguration="false"/>  prohibit validation of integration mode to avoid errors. More knowledge of the principle, please give me a lot of advice! 

IIS7.0 detected a workaround (GO) error for the ASP. NET settings that are not applicable in integrated managed pipeline mode:

To modify the configuration:

After you change to Classic mode, another error may occur ... Such as:

This error is that the ISAPI disabled some components, because the. NET Framework 4.0 is installed, may be disabled by IIS by default, so open the Settings page, sure enough, 32-bit and 64-bit ASP.

Resolves a workaround for an ASP. NET setting that is not applicable in integrated managed pipeline mode (not simply set to Classic mode). -Catcherx