I recently renamed my root TFS folder from D:\TFS\systemstfs
to 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:
- Enabling "break on CLR exceptions when thrown"
- Re-getting the solution from TFS
- Rebooting
- Switching to use IIS and then back to Express
- Googling 500.19, 0x80070003, wrong path, cannot read configuration file, and various combinations of those terms
But have had no luck. Has anyone come across this before?
Here is another possible solution that doesn't involve fishing for the
applicationhost.config
file:In my case I also needed to change authentication mode which can be done via:
In my case, the following changes resolved this error:
Open
applicationhost.config
file from[SolutionFolder]>.vs[Hidden Folder]
and change the value ofoverrideModeDefault
attribute inwindowsAuthentication
section from Deny to Allow. As shown below.If you are using Local IIS Web Server, rename the custom virtual directory, save and try again. After this, you can put back the original name.
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
Fix
In my case, the wrong path was recorded in a .vs folder in the zip i received from colleague. Normally, I'd get source through source repository where .vs is not checked in.
Deleting the .vs folder resolved the problem for me.
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.
Using Visual Studios 2015.