IIS 7 and Above
HTTP Error 500.19 - Internal Server Error 0x80070003
Last post Sep 12, 2012 01:45 AM by ethiopian1987
May 28, 2009 01:52 PM|lowlow|LINK
I know the topic is very common in ISS but I couldn't solve it with what I found so far.
I have got IIS7 running on my Windows 2008 Server SP2 x64. It works perfectly when I have my websites located in the standard C:\inetpub\
Because of the way my machine is set up, I need to relocate the website to a network drive, that being Z:\WWWROOT\inetpub\wwwroot . Z is the network drive. No credentials are needed to access the drive.
When I copy the path above in my browser the folder containing the index.htm is displayed correctly.(in firefox, not in IE)
I have correctly set the IIS_IUSRS permissions on the site folder (and just in case, I made a new site folder via IIS so it set it's own permissions) yet I keep getting the error:
Internet Information Services 7.0
Thanks in advance for a solution!
May 28, 2009 02:43 PM|rlucero|LINK
The issue isn't permissions or access at this point. IIS is unable to read the configuration file in the path specified.
Try copying, then deleting the web.config file and see if that solves your serving problem. If it does, then use the IIS UI to navigate to the website and pinpoint the config error.
May 28, 2009 03:23 PM|lowlow|LINK
Thanks for your reply but haven't got a file web.config.
I eventually even searched my C: for it and didn't find it.
May 28, 2009 03:26 PM|rlucero|LINK
According to the error you've posted it has these two lines:
Does a web.config file exist at this path?
May 28, 2009 03:39 PM|lowlow|LINK
For sure there isn't. I nowhere have a web.config on my system nor on my network drive (X:). When I use C:\inetpub it works fine although there's no web.config either.
Thx in advance !
May 28, 2009 03:52 PM|rlucero|LINK
Can you double check the permissions on the Z:\WWWROOT\inetpub\wwwroot\ folder? IIS_IUSRS needs Read & Execute, List Folder Contents and Read permissions.
Maybe the worker process can't correctly access the folder? That's my next guess.
May 28, 2009 03:58 PM|lowlow|LINK
Wasn't the case for that specific dir, changed it but the problem persists! Same error message.
May 28, 2009 04:54 PM|anilr|LINK
You cannot point IIS to a mapped network drive since the mapped network drive only exists in your session, not the session IIS is running as - use the
\\server\share syntax to point IIS to a network drive and configure a username/password to connect to that drive if needed.
May 29, 2009 07:11 AM|lowlow|LINK
Thx for you reply, how would that look like in my case? I tried...
Thanks in advance
Jun 01, 2009 03:09 PM|anilr|LINK
You must have done "net use z: \\server\share" - instead of using z:, use
\\server\share in the IIS configuration - so
\\server\share\wwwroot\inetpub\wwwroot - also may need to specify username/password in "connect as".
Jun 02, 2009 01:24 PM|lowlow|LINK
Thanks but I keep on getting an 500.19 error: I made a user with admin rights on the 192.168.0.40 machine and I'm logged on with this credentials. I used the \\server\share\... as you suggested. Still:
<virtualDirectory path="/" physicalPath="\\192.168.0.40\Volume_1\inetpub\wwwroot" userName="\\192.168.0.40\Volume_1\wwwrootuser" password="[enc:AesProvider:S9FRXhSPCENhWQXjBzMNdQBxzKtuAXRI2f2Q3a0X7gPc//yJUwLsTItYL8N6GKXO:enc]" logonMethod="ClearText" />
View more information »
Jun 02, 2009 04:23 PM|anilr|LINK
Pretty sure that \\192.168.0.40\Volume_1\wwwrootuser is not a valid username.
Jun 21, 2009 09:18 PM|Xiaoth|LINK
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.
Aug 29, 2012 05:32 PM|ojm37|LINK
Hmmm. I'm getting the same error message, different details. In my case, it says the config file is located at
Not sure why it says that: there is no ProjectFiles directory (there used to be, but it was for a totally different project). So why is this site pointing to a non-existent directory for a different project? AND, how the BLEEP do I tell it NOT TO LOOK THERE?!?!?!
Sep 12, 2012 01:45 AM|ethiopian1987|LINK
This error is one I have received as well, although I did mine on purpose.
To fix this type of error go to C:\Windows\System32\drivers\etc and open the hosts file with notepad. If you see something like this:
# Copyright (c) 1993-2009 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 184.108.40.206 rhino.acme.com # source server
# 220.127.116.11 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
(Please note that the bold lines can appear different depending on what windows os you are running)
then remove the lines with no # as they will cause this error. The web.config file does not exist on any windows xp, vista or 7.
I hope this helps if your hosts file is corrupted though you might want to get a fix from this site: http://support.microsoft.com/kb/972034 and download the microsoft fixit tool.