CODEWITHSUNDEEP
asp.net.netiisvisual-studio-2013
user3171214
user3171214

Reputation: 569

Visual Studio 2013. You do not have sufficient privilege to access IIS web sites on your machine

I just installed VS2013 and turned on IIS 7 on my Windows 7 Ultimate x64 machine. When trying to open a solution I get:

Creation of the virtual directory localhost:xxxxx failed with the error: Unable to access the IIS metabase. You do not have sufficient privilege to access IIS web sites on your machine.

I tried running Visual Studio 2013 as Administrator (right click, run as administrator), still the same error. I also did aspnet_regiis -i and it didn't help either.

Upvotes: 56

Views: 83154

Answers (12)

Jitendra Kumar
Jitendra Kumar

Reputation: 2221

Just delete .vs folder in Project (It may be hidden) and again open project in visual studio, it will be work.

Upvotes: 0

Miguel
Miguel

Reputation: 1714

Visual Studio 2015: Just start Visual Studio "as administrator" that worked for me without having to make any changes to VS or registry.

Upvotes: 0

Andrew Gale
Andrew Gale

Reputation: 107

Tried everything suggested, finally turned out we had to install IIS 10.0 Express with Application Compatibility Database installed by default

Screenshot:

Programs screenshot

Upvotes: 0

Raj Chaurasia
Raj Chaurasia

Reputation: 1974

Go to C:\Windows\System32\inetsrv. Click config folder. You will get a popup - "You don't have access to this folder - Click continue to permanently get access to this folder". Perform same for Export folder which is inside config folder. You should be able to open the solution and the web application project will be deployed on IIS.

enter image description here

Upvotes: 196

Polymorphic
Polymorphic

Reputation: 430

I encountered similar problem. I had not installed IIS yet. 1. I installed IIS. 2. I used aspnet_regiis tool (with -i) to enable Asp.Net on IIS. 3. Tried to load existing web app project. (FAILED with same error) 4. I reset IIS service. 5. I opened VS2013 as administrator and loaded the existing web app project (Succeeded) 6. The virtual directory created on IIS successfully.

I think the key is the Aspnet_regiis IIS reset and IIS service reset steps.

Upvotes: 0

spryce
spryce

Reputation: 607

The highest voted answer here did not work for me. I've recently upgraded to Windows 10 (ungh) and when I went to:

C:\Windows\System32\inetsrv

...I did not get a permissions pop up. Further more when I tried to change the permissions manually, most of the options were not available or greyed out.

The end fix was to click into each folder individually inside the inetsrv directory. When I did this I received a pop up for each folder where I could gain access.

Restarted VS and voilà!

Upvotes: 2

PaisaJR
PaisaJR

Reputation: 111

I had tried each of the steps recommended and didn't work. So, my last resource was to review the registry to find out if my user was pointing to a temp or cache folder. Some posts were suggesting to check on HKEY_LOCAL_MACHINE; but those were. So, I finally found it by going into the HKEY_CURRENT_USER as recommended by boilers222:
Opened registry (CTRL-R, regedit, OK) Navigated to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\ Found the Personal key was pointing to "\OurServer\RedirectedFolders\MyName\MyDocuments" Selected the Personal key, right clicked on it, and selected Modify
Entered a location pointing to my user's documents file: "%USERPROFILE%\Documents\" Clicked OK and closed the registry editor When I opened Visual Studio and opened my solution, it loaded without the "unable to access the IIS metabase" error.

Upvotes: 11

Orcun Berkem
Orcun Berkem

Reputation: 111

Try running VS as admin. If it does not work check if you have IIS metabase folder permission. Open up windows explorer (Win + e). Type the following to address bar:

win 7, win 8.1, win 10 %systemroot%\System32\inetsrv\config

win 8 professional %systemroot%\inetsrv\config

Allow access if needed. Go into \Export\ folder and allow access again.

Source here

Upvotes: 10

Curt Miller
Curt Miller

Reputation: 17

There is a simple answer. Make sure you start VS 20xx as an administrator. This is required for Azure development as well.

Upvotes: 0

Mark Burgess
Mark Burgess

Reputation: 11

On Windows 10 running Visual Studio 2015 Community Edition, here are the steps I followed:

  1. Control Panel -> Programs and Features -> Turn Windows Features on or off... inside that, we had to select Internet Information Services -> Web Management Tools -> IIS 6 Management Compatibility -> IIS Metabse and IIS 6 configuration compatibility.

  2. select "Troubleshoot Program" check "The program requires additional permissions" click "Next", click "Test the program..." wait for the program to launch click "Next" select "Yes, save these settings for this program" click "Close"

  3. Go to C:\Windows\System32\inetsrv. Click config folder. You will get a popup - "You don't have access to this folder - Click continue to permanently get access to this folder". Perform same for Export folder which is inside config folder.

Then it finally got past the permission issue.

Upvotes: -1

dannash918
dannash918

Reputation: 454

The root cause of this error for me was that IIS was installing the config folder on a network shared drive at my workplace. I had to change this to use a local drive and it fixed it.

IIS creates an IISExpress folder in your %USER_HOME%/Documents folder (which for me was a shared drive)

For me this issue was solved by uninstalling IIS, and clearing everything IIS related in the registry. I then had to change my Documents drive in Registry (KHCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders) from a shared drive to a local drive (C:\Users[profile]\Documents).

Then reinstall IIS. It should create an IISExpress in the new Documents folder.

Upvotes: 14

Galaxydreams
Galaxydreams

Reputation: 319

In Windows 8, you have to right-click devenv.exe and select "Troubleshoot compatibility".

select "Troubleshoot Program"
check "The program requires additional permissions"
click "Next", click "Test the program..."
wait for the program to launch
click "Next"
select "Yes, save these settings for this program"
click "Close"

Upvotes: 13

Related Questions