The solution to ASP. NET settings that are not applicable in integrated managed pipeline mode is detected (not simply set to [classic] mode )., Not applicable to asp.net

The solution to ASP. NET settings that are not applicable in integrated managed pipeline mode is detected (not simply set to [classic] mode )., Not applicable to asp.net
I recently learned ASP. NET/from the video of Chuanzhi podcast. After a project is configured, I always report

HTTP 500.23-Internal Server Error

Detected ASP. NET settings that are not applicable in integrated managed pipeline mode.

 

I am so worried that I have finally solved the problem after searching for a long time. I hope I can help you with the record!

 

Directory (?) [-]

 

We port the ASP. NET program from IIS6 to IIS7, and the following error may occur:

HTTP 500.23-Internal Server Error
Detected ASP. NET settings that are not applicable in integrated managed pipeline mode.

Why are the above errors?

The IIS7 application pool has two modes: "integration mode" and "Classic mode ".

Classic mode is the way we used to use IIS 6.

If you use the integration mode, you need to modify the configuration file for the custom httpModules and httpHandlers and transfer them to the <modules> and

Two solutions:

Method 1: configure the application pool

Configure the application pool on IIS7 and change the mode of the application pool to "classic". Then everything works normally.

Enter the error message prompted above in the search engine, and almost all the searched results are directly changed to "classic.

However, this is only a matter of expediency. IIS7.x is used, but only six functions are used. In addition, some ASP. net mvc programs do not work well. Therefore, we try the following solutions:

The second method is to modify the web. config configuration file:

For example, the original settings (You may not have the httpModules or httpHandlers node in your environment)

<system.web>    ............    
When the IIS7 application pool is "integration mode", change:
<system.web>    ...........</system.web><system.webServer>    <modules>      <add name="MyModule" type="MyApp.MyModule" />          </modules>    
(If your web. config does not have an httpModules or httpHandlers node, add the following directly to the node system. webServer:
<Validation validateIntegratedModeConfiguration = "false"/> disable integration mode verification to avoid errors. For more principles, please give me more advice!

IIS7.0 detected a solution (to) error that is not applicable to ASP. NET settings in integrated managed pipeline mode:

 
Modify Configuration:
After changing to the classic mode, another error may occur... For example:
 
 
 
This error indicates that some components are disabled by ISAPI because. NET Framework 4.0 installation, may be disabled by IIS by default, so open the settings page, it is true that the 32-bit and 64-bit ASP. NET 4.0 components are set as "not allowed.
 
 
 
 
 
Allow the two ASP. NET V4.0 components to run the website successfully!