PDA

View Full Version : HTTP Error 500.22 - Internal Server Error


newcents
03-05-2008, 11:29 AM
I sent this to discountasp.net support and they said it was outside of their expertise and I should post it here. Any help appreciated. I don't have a web.config in the root directory of the app or anything else:
http://tosdevelop1.web701.discountasp.net/






Error Summary
HTTP Error 500.22 - 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 0x80070032
Requested URL http://tosdevelop1.web701.discountasp.net:80/highslide_iframe_ajax_parent_update/example-iframe.html
Physical Path e:\web\tosdevelop1\htdocs\highslide_iframe_ajax_pa rent_update\example-iframe.html
Logon Method Not yet determined
Logon User Not yet determined
Most likely causes:

* This application defines configuration in the system.web/httpModules section.

Things you can try:

* Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line - for example, %SystemRoot%\system32\inetsrv\appcmd migrate config 'Default Web Site/'. Using AppCmd to migrate your application will enable it to work in Integrated mode, and continue to work in Classic mode and on previous versions of IIS.
* If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.
* Alternatively, switch the application to a Classic mode application pool - for example, %SystemRoot%\system32\inetsrv\appcmd set app 'Default Web Site/' /applicationPool:'Classic .NET AppPool'. Only do this if you are unable to migrate your application.

(Set 'Default Web Site' and 'Classic .NET AppPool' to your application path and application pool name)
Links and More Information Integrated mode is the preferred mode for running ASP.NET applications on IIS 7.0.

View more information »

bruce
03-12-2008, 01:24 AM
The web.config schema is slightly different between IIS 6 & IIS 7 to accomodate for delegated administration through the web.config file.


This error message means that there are some attribute in your web.config file that are invalid.
Do you have IIS 7 installed? If so, you can use the appcmd.exe to update the web.config file.

Alternatively, you can also switch the Application Pool pipeline mode to "Classic" but you'll lose some new feature of IIS7.

Bruce

DiscountASP.NET
www.DiscountASP.NET (http://www.DiscountASP.NET)

wisemx
03-12-2008, 01:32 AM
I just took a look at it and the Ajax tests all succeeded...Did you get it worked out?

mjp
03-15-2008, 09:10 AM
newcents said...
I sent this to discountasp.net support and they said it was outside of their expertise and I should post it here.


What they probably said was it was outside the scope of our support (rather than their expertise). Maybe a subtle distinction, but one I wanted to make clear.


We prefer to handle certain issues through the forum for many reasons, but primarily, we do not assist with coding issues through helpdesk tickets because it opens a can of worms ("Hey, you guys fixed this script a month ago, now it's broken again!"). It's much better to do it here in the open where the next person with the same issue can benefit from the answers from other users (or DiscountASP.NET staff).


The support staff are actually not allowed to make any changes to customer apps or code, or do any in-depth troubleshooting, even if they are quite capable of doing so. There are hosts that allow support staff to open up your files and make changes to them. That may solve your immediate problem (or make it worse), but in the long run it is not a sound - or sustainable - practice.


So when support says something is "outside the scope of support that we provide," those are the reasons why.


Didn't mean to sidetrack the thread, just wanted to clarify that.

mjp
---
DiscountASP.NET