Server Error: HTTP Error 500.19 - Internal Server Error

Chicago Area Laptop for rent: $35 per day plus $10 for additional day

Situation: When accessing website in Windows 2008 IIS, you may receive this error: HTTP Error 500.19 - Internal Server Error
Description: The requested page cannot be accessed because the related configuration data for the page is invalid. Error Code: 0x80070005 Notification: BeginRequest Module: IIS Web Core Requested URL: http://localhost:80/
Physical Path: C:\Testsite
Logon User: Not yet determined
Logon Method: Not yet determined
Handler: Not yet determined
Config Error: Cannot read configuration file Config File: \\?\C:\Test\ProductsService\ProductsService\web.config Config Source:

Case 1: I just did not installed some IIS components. After adding ASP.net, website starts to works fine.

Case 2: It turned out that my root web was working fine, but my subwebs were not working fine and I got this error for the subweb. The subweb was an individually configured ASP.NET application. I figured that this wasn't important because the root web was just a flat HTML file, but it mattered.
What happened in my case was that a few days ago I had relocated the root web, then updated IIS to point to the new directory. All of the subweb applications, however, were treated by IIS as virtual directories, each with its own physical directory mapping. So each had the stale path.
More specifically, I moved "C:\web\www.mysite.com" to "C:\web\mysite.com", updated IIS for MySite to point to \web\mysite.com, and left it as such. The applications under mysite.com were each pointing to C:\web\www.mysite.com\[application].
I had to update each subweb application's Basic Settings to point to the revised path, and the 500.19 error went away.

Case 3: This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error. Check the web application folder permission and make sure the following users and groups are included \ASPNET and \IIS_IUSRS and \IUSR.

Case 4: This error also occurs when you have accidentally renamed the directory that contains your application when you are "localhosting" for development. That's what I did. IIS was complaining because it could no longer find the physical directory.

Case 5: his problem happened to me because i set the Framework of my website to 4.0 while the config of a webpage in subfolder where .net framework 3.5

Post your questions, comments, feedbacks and suggestions

Contact a consultant