Asp. NET program migrated from IIS6 to IIS7 500.22 error

The most probable cause:
• This application is system.web/The configuration is defined in the httpmodules section.
Actions you can try:
• Migrating configurations to system.webserver/Modules Festival. You can do this manually, or by using APPCMD on the command line-For example%SystemRoot%\system32\inetsrv\appcmd Migrate Config"Default Web site/"。 Migrating an application with APPCMD will enable it to work in integrated mode and continue to work in Classic mode and previous versions of IIS.
• If you are sure you can ignore this error, you can pass the system.webserver/[email protected] set toFalseTo disable it.
• You can also switch applications to the Classic mode application pool-For example%systemroot%\system32\inetsrv\appcmd set app < Span style= "color: #800000;" > "default web site/"  / Applicationpool: "classic .net apppool< Span style= "color: #800000;" > ". Do this only if you cannot migrate the application.  
(set "Default web site" and "Classic .net apppool" to your application path and application pool name)  
The link and more information integration modes are in  iis 7.0  runs  asp. net  Application Preference Mode

{The application pool for IIS is divided into two types based on managed pipeline mode: integrated and Classic

In integrated. NET mode, applications should not specify the ASP in the <system.web>/

The Classic . NET pattern is the way we used to be in IIS 6, without the above limitations. }

Workaround:

Method 1 configures the application pool on IIS7.

Method 2: Add our Module (modules) to IIS7

Reference: http://aabs.wordpress.com/2007/11/16/ihttpmodule-not-running-after-conversion-to-iis-7-and-net-35/

Method 3: Modify the Web. config

Learn MORE:

IIS7 's application pools has two mode, one is integrated and the other is classic. If you use Integrated mode, you will need to change the configuration files for your custom httpmodules and httphandlers, and transfer them to <modules> and

What is the difference between the two modes of IIS7 and IIS6?

IIS7.0 Integrated mode:ASP. Modules and handlers from <system.webServer> <modules> and

IIS7.0 Classic mode: the opposite of,<modules> and

IIS6.0: This is not a stranger to everyone.

What if I do a configuration that can be run in both IIS6 and IIS7 mode? What is validateintegratedmodeconfiguration= "false" for? If you need a friend, you can check the details here .

Secondly, after migrating from IIS6 to IIS7, some URL rewrite functions may not be useful, and the following article describes a hack method that effectively controls the duties of Staticfile handler. The way of working like IIS6 is realized.

Example code:

<system.web> <!-- Modules for IIS 6.0 and IIS 7.0 Classic mode ---<httpmodules> <add name="magicajaxmodule" type="magicajax.magicajaxmodule, Magicajax "/> </httpmodules> <!-- handlers for IIS 6.0 and IIS 7.0 Classic mode ---

<httphandlers>

<AddPath= " "= "/>

</httphandlers>

</system.web> <system.webserver> <!-- Modules for IIS 7.0 Integrated mode --<modules> <add name="magicajaxmodule" type="magicajax.magicajaxmodule, Magicajax"/> </Modules> <!-- handlers for IIS 7.0 Integrated mode --

<handlers>

<AddName="MyHandler"Path="*.myh"Verb="get " precondition= " "/>

</handlers>

<!-- Disable detection of IIS 6.0/classic mode asp . <validation validateintegratedmodeconfiguration= "false"/> </system.webserver>