An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode
July 26th, 2009 by Andrew Chen
I was trying out IIS7 the other day. When I was trying to set up a new site I got the following error message.
Error Summary
HTTP Error 500.24 - Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
Detailed Error Information
Module ConfigurationValidationModule
Notification BeginRequest
Handler StaticFile
Error Code 0×80070032
Requested URL http://www.gadgetroute.com:80/default.htm
Physical Path C:\testweb\default.htm
Logon Method Not yet determined
Logon User Not yet determined
Most likely causes:* system.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.
* Move this application to an application pool using Classic .NET mode - for example, %SystemRoot%\system32\inetsrv\appcmd set app “Default Web Site/” /applicationPool:”Classic .NET AppPool”(You can set “Classic .NET AppPool” to the name of another application pool running in Classic managed pipeline mode)
Links and More Information If you are not sure or unable to use the first two options, then it is preferred that you move this application to Classic mode.
The solution it suggest is not straight forward enough. Simply put the error can be corrected by adding the following bold line in the web.config file
<configuration>
<system .webServer>
<validation validateIntegratedModeConfiguration=”false” />
</system>
</configuration>
Related Posts:
2 Comments
Sorry, the comment form is closed at this time.


hey it worked like a charm. great share
Everything is right instead of
please write