Reputation: 1989
I'm trying to open an asp.net MVC project in Visual Studio 2013 on a Windows 7 machine. I'm getting an error about being unable to access the IIS metabase. I've tried every suggestion I could find on the web, but am unable to get this to work. The major change at our company is that our local file server went down. This held all of My Documents. I'm guessing that there was something in there that I need, but I don't know what that file is or how to restore it. I'm unable to make any changes to sites and my bosses are hounding me to get changes done, so I'm pretty desperate. Can someone give me a solution?
If I open the site using the Visual Studio solution file, I get a message saying that the project failed to load. If I right click on it and choose reload, I get a message saying, "Creation of the virtual directory http://localhost:1436/ failed with the error: Unable to access the IIS metabase. You do not have sufficient privilege to access IIS web sites on your machine."
If I open the site as a web site (not using the solution or project files), I get the error "Configuring IIS Express failed with the following error: Unable to access the IIS metabase. You do not have sufficient privilege to access IIS web sites on your machine."
Here's a list of everything I tried. This seems to be most of the ideas people have had, but I'm hoping there's another solution out there you can come up with.
Went to %systemroot%\System32\inetsrv\config
Uninstall/Reinstall IIS
Repaired Visual Studio 13
Change .csproj file
<UseIISExpress>false</UseIISExpress>
<UseIIS>False</UseIIS>
<IISUrl></IISUrl>
Ran Visual Studio as administrator
Deleted the default web site and recreated it
Repaired IIS
Tried giving Default App Pool access to inetsrv folder
Checked the registry key in HKEY_LOCAL_MACHINE
Upvotes: 5
Views: 3315
Reputation: 1989
Found a solution to my problem.
I had found a suggestion to check the registry in HKEY_LOCAL_MACHINE to make sure the values were not pointing to a server or other location that did not exist. I thought this made since because I know I'd lost connection to a server. But when I checked the values there, they were already pointing to my C drive. Here's the link where I found this suggestion: Visual Studio 2013. You do not have sufficient privilege to access IIS web sites on your machine.
Did some more digging and finally found a value in HKEY_CURRENT_USER that was pointing to our crashed server. I changed the value to point to the C drive and Visual Studio opened without any problems!
Here's the steps I took:
Upvotes: 6