A workaround for ASP.net settings that are not applicable in integrated managed piping mode is detected (not simple to Classic mode). -Catcherx__.net

We ported the ASP.net program from IIS6 to IIS7 and may run the following error:

HTTP error 500.23-internal Server error

detects asp.net settings that are not applicable in integrated managed piping mode.

Why the above error occurs.

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

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

If you use Integrated mode, you will need to modify the configuration files for the custom httpmodules and httphandlers, and then transfer them to the <modules> and

two ways to solve this problem: The first method, configuring the application pool

Configure the application pool on the IIS7 and change the program pool mode to "classic", after which everything is OK. As shown in figure:

The search engine entered the error message above, almost all of the results were directly changed to "classic" and tasted.

But this is only a stopgap, with the iis7.x, but actually played only 6 of the function, in addition, in some asp.net MVC program, the effect is not good, so we try the following workaround: The second method, modify Web.config configuration file:

For example, previous settings (you may not have httpmodules,httphandlers nodes in your environment)

<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>
    
 
(If your web.config does not have a httpmodules,httphandlers node, add it directly to the node system.webserver:

<validation validateintegratedmodeconfiguration= "false"/>  
prohibit validation of integration mode to avoid errors.

more principles of knowledge, please give a lot of guidance.
 
 
 
 
IIS7.0 detects workaround for asp.net settings that are not applicable in integrated managed piping mode (RPM) 
Error screenshot: 


Modify Configuration screenshot: when you change to Classic mode, another error may occur ... The following figure:




The error is that the ISAPI disables certain components because the. NET Framework 4.0 is installed and may be prevented by IIS from running by default, so the Settings page opens, and sure enough, the 32-bit and 64-bit ASP.net 4.0 components are set to Disallowed.





By allowing two ASP.net V4.0 components to pass, the site will run successfully.