Server Error: HTTP Error 500.19 - Internal Server Error

Question

User-264353060 posted

I got the following error while trying to make a test WCF project on Vista

Server Error<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>

---

HTTP Error 500.19 - Internal Server Error<o:p></o:p>Description: The requested page cannot be accessed because the related configuration data for the page is invalid. <o:p></o:p>Error Code: 0x80070005 <o:p></o:p>Notification: BeginRequest <o:p></o:p>Module: IIS Web Core <o:p></o:p>Requested URL: http://localhost:80/ProductsService/ProductsService.svc <o:p></o:p>Physical Path: C:\Test\ProductsService\ProductsService\ProductsService.svc <o:p></o:p>Logon User: Not yet determined <o:p></o:p>Logon Method: Not yet determined <o:p></o:p>Handler: Not yet determined <o:p></o:p>Config Error: Cannot read configuration file <o:p></o:p>Config File: \\?\C:\Test\ProductsService\ProductsService\web.config <o:p></o:p>Config Source: <o:p></o:p>

-1: <o:p></o:p>     0: <o:p></o:p>

<o:p></o:p>More Information... 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. <o:p></o:p>

---

Server Version Information: Internet Information Services 7.0

 

I also found a simple solution to it. You can check at http://www.vishwamohan.com/ShowArticle.aspx?ArticleID=30

 

Answer 1

User1395367073 posted

This seems similiar to an issue I had.  It turned out to be a security setup issue.  Check the web application folder permission and make sure the following users and groups are included \ASPNET and \IIS_IUSRS and \IUSR. 

Answer 2

User-1540559508 posted

This might not help, but I wanted to comment that I spent hours on this same error and found the solution to my problem. It turned out to be something that nobody else ever documented, so I'm trying to spread the word for Google.

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.

Hope this helps others like it would've helped me.

Jon

Answer 3

User-2071498389 posted

Hi all

 

I had the same problem ,, this video helped me alot

 

http://www.youtube.com/watch?v=vBNoTK31zPo

 

I just did not installed some components, after the installation my website starts to works fine 

Answer 4

User1611804580 posted

This might not help, but I wanted to comment that I spent hours on this same error and found the solution to my problem. It turned out to be something that nobody else ever documented, so I'm trying to spread the word for Google.

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.

Hope this helps others like it would've helped me.

Jon

Thank you so much!

I wasted 3 hours on this problem, and your post solved my headaches at once =]

Answer 5

User-1103677793 posted

I want to say thanks to Liquid Snake. I received the same error message, watched the YouTube video he (or she) recommended (making the selections recommended by the video), and this installation solved my problem as well.

Answer 6

User-1125611039 posted

Thanks Wrabadi, it worked for me. 

Answer 7

User-106920107 posted

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.  

Ooops! 

Answer 8

User-110847984 posted

this 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

i am not sure