Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

HTTP Error 500.22 - Internal Server Error (An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.)

I receive this error when I view an application.

HTTP Error 500.22 - Internal Server Error (An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.)

.Net framework 2.0, 3.5 and 4 are installed and I am using SQL 2008. Can anyone tell me what the solution is for this error?

like image 865
Varun Shenoy Basty Avatar asked Sep 10 '11 08:09

Varun Shenoy Basty


People also ask

How do I change managed pipeline mode in Visual Studio?

option-1: In Visual Studio goto WebSite/WebApplication properties and change Managed Pipeline Mode to 'Classic'. option-2: Open %userprofile%\documents\iisexpress\config\applicationhost. config and locate your site in "Sites" section and change the app pool to classic (say Clr4ClassicAppPool ).

How do I change managed pipeline mode in IIS?

Once inside IIS Manager, Select Application Pools in the left pane. Once selected, the application pools available for your web server will be displayed on the right. To toggle the Management Pipeline Mode setting for this application pool, simply double click the application pool.

How do you set system Web identity impersonate is set to true?

web/identity@impersonate is set to true. Things you can try: If the application supports it, disable client impersonation. If you are certain that it is OK to ignore this error, it can be disabled by setting system. webServer/validation@validateIntegratedModeConfiguration to false.


2 Answers

This issue is caused by the pipeline mode in your Application Pool setting that your web site is set to.

Short

  • Simple way Change the Application Pool mode to one that has Classic pipeline enabled.
  • Correct way Your web.config / web app will need to be altered to support Integrated pipelines. Normally this is as simple as removing parts of your web.config.
  • Simple way (bad practice) Add the following to your web.config. See http://www.iis.net/ConfigReference/system.webServer/validation

     <system.webServer>      <validation validateIntegratedModeConfiguration="false" />  </system.webServer> 

Long If possible, your best bet is to change your application to support the integrated pipelines. There are a number of changes between IIS6 and IIS7.x that will cause this error. You can find details about these changes here http://learn.iis.net/page.aspx/381/aspnet-20-breaking-changes-on-iis-70/.

If you're unable to do that, you'll need to change the App pool which may be more difficult to do depending on your availability to the web server.

  • Go to the web server
  • Open the IIS Manager
  • Navigate to your site
  • Click Advanced Settings on the right Action pane
  • Under Application Pool, change it to an app pool that has classic enabled.

Check http://technet.microsoft.com/en-us/library/cc731755(WS.10).aspx for details on changing the App Pool

If you need to create an App Pool with Classic pipelines, take a look at http://technet.microsoft.com/en-us/library/cc731784(WS.10).aspx

If you don't have access to the server to make this change, you'll need to do this through your hosting server and contact them for help.

Feel free to ask questions.

like image 186
Kirk Avatar answered Sep 23 '22 06:09

Kirk


In your web.config, make sure these keys exist:

<configuration>     <system.webServer>         <validation validateIntegratedModeConfiguration="false"/>     </system.webServer> </configuration> 
like image 33
user3564057 Avatar answered Sep 23 '22 06:09

user3564057