I recently renamed my root TFS folder from
D:\TFS\sys because one of the project's paths was too long for Windows. Now, when I attempt to run a different project (D:\TFS\sys\companydomain.com\Dev\Flowers\wsBusinessLayer) in VS2013 using IIS Express (Project URL http://localhost:59729/Flowers/wsBusinessLayer/) I get the following error message in the browser:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Module - IIS Web Core
Notification - BeginRequest
Error Code - 0x80070003
Config Error - Cannot read configuration file
Config File - \?\D:\TFS\systemstfs\companydomain.com\Dev\Flowers\web.config
Requested URL - http://localhost:59729/Flowers/wsBusinessLayer/InformationServices.asmx
Physical Path - D:\TFS\sys\companydomain.com\Dev\Flowers\wsBusinessLayer\InformationServices.asmx
(emphasis mine, D: is the second HDD on my machine, not a network share)
It's clear to me what the problem is (the config file path is wrong) but I have no idea how to fix it. I have tried:
But have had no luck. Has anyone come across this before?
Here is another possible solution that doesn't involve fishing for the
In my case I also needed to change authentication mode which can be done via:
Turns out I had to edit
%USERPROFILE%\Documents\IISExpress\config\applicationhost.config in the following way -
<configuration> <system.applicationHost> <sites> <site name="wsBusinessLayer"> <application path="/"> <virtualDirectory path="/Flowers" physicalPath="D:\TFS\sys\companydomain.com\Dev\Flowers" />
I don't know how this file gets changed "properly", but editing it manually worked fine.
In my case, the following changes resolved this error:
applicationhost.config file from
[SolutionFolder]>.vs[Hidden Folder] and change the value of
overrideModeDefault attribute in
windowsAuthentication section from Deny to Allow. As shown below.
Changing the port number on my MVC project resolved my issue. I went in circles for over an hour looking for an answer. Thank you Sonic Soul.
It always amazes me when one tiny tweak can fix something horribly broken.
I incremented the port number and the error magically resolved.
Project Properties > Web > Project Url
Using Visual Studios 2015.
I got the same error on IIS 8.5 (not express)
For me it was because I had replaced the folder with a copy and renamed it while IIS was running. For some reason it kept erroring out. I had to remove the website definition from IIS and re add it to get it to work.
Had the same issue today.
Change that caused the issue
Moving functionality from a separate controller to home controller. I literally moved a view and the functionality behind it from Controller'X' to HomeController
Nature of the issue
In my case I replace
.. in my path with a normal folder path.
I did the "clever" trick of utilising the relative path of my script file as I did not want to hard code my folder address.
"C:\Program Files\IIS Express\iisexpress.exe" /path:"%~dp0..\Lagardsdorren\bin\Debug\netcoreapp2.2\publish" /port:44342
I knew, but it took my some time to realise, that
.. is non grata in IIS(express) as it makes it possible to path yourself out of your sites home directory. In my case it didn't but I guess IIS(express) just stops anything with
.. in it.
I don't know how to get back to my clever relative path, but that is for another question.
If using a Virtual machine with "Shared Folders" -- I was using Workstation Pro to share the folder. When the project was in the "Shared folder" that was hosted on the HOST PC I was unable to run the project. Moving the project to a "Local" Drive resolved for me.
My setup is a .NET 4.6.1 MVC project hosted as an Azure Cloud Service. I got this error when running locally with Visual Studio 2019 and IIS Express. I was able to fix the error. In my case the error was a red herring and was a symptom of another problem. For me, I had to remove my references to System.http.net, System.runtime, and System.Runtime.InteropServices. Then I added the latest version of those those three references back with Nuget.
The issue was that my code could not find those three packages. It has issues finding the packages every time I switch my git branch, but that's a completely separate error, and one I'm still trying to resolve. The way I figured out what was wrong was I would run the code and look at the "build" and "debug" output in Visual Studio 2019. I saw errors relating to the code not being able to find System.Http.Net, so I fixed that, then saw the errors with the other packages and fixed them. The real issue was that my code was getting exceptions and not running correctly, it just happened to manifest as this 500.19 error.
Another possibly contributing factor is that I disabled "just my code" earlier in the day. This seemed to cause my code to not break when exceptions were encountered. Once I turned this back on, my code would break when an exception happened, and this also helped me figure out the cause of the problem. To find this option, go into Tools > Options > Debugging > General > "Enable Just My Code".
User contributions licensed under CC BY-SA 3.0