IIS 500.19 error on ASP.NET 4.0 sub-application

5

I've created a "test" application below the main application on my website which is an exact duplicate of the main application - I use the /test app to test new changes before putting them in production.

After upgrading the app from .NET 3.5 to .NET 4.0, my /test application refuses to run, returning a 500.19 error from IIS. My main application (and another sub-app at the same level as /test) runs just fine.

I found a lot of references about the 500.19 error and they usually boil down to some line in the web.config that is invalid.

However, in my case the error doesn't point me to any specific line -- the error message is copied below, note that the "Config Source" section is empty.

Error Summary
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.


Detailed Error Information
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x800700b7
Config Error 
Config File \\?\c:\blahblahblah\test\web.config
Requested URL http://localhost:80/blahblahblah/test
Physical Path C:\blahblahblah\test
Logon Method Not yet determined
Logon User Not yet determined
Config Source

   -1: 
    0: 

Any clues would be appreciated!

asp.net
asked on Stack Overflow Oct 17, 2010 by Marty

3 Answers

3

Glad you're sorted now.

For me (and these guys) this error was a due to the URL Rewrite Module not having been installed - look for a 'rewrite' section in the web.config.

answered on Stack Overflow Sep 29, 2011 by Dunc • edited Sep 29, 2011 by Dunc
0

Nevermind... ;-)

The problem was because of a duplicate section where I forgot to add a section before the for a custom provider. (at the same time that I upgraded to .NET 4.0, I added a custom provider for encrypting sections of my web.config...)

I found the error the old-fashioned brute force way by commenting one chunk at a time in the config file until it started working...

answered on Stack Overflow Oct 17, 2010 by tippmar
0

This error might also be related to trying to run a .net 4.0 application on a IIS that has not been -iisreg with the .net 4.0 path

answered on Stack Overflow Oct 17, 2010 by citronas

User contributions licensed under CC BY-SA 3.0