Question

0

NuGet Access Denied

Jay Greentree posted 8 Years Ago

I had to reinstall Windows server yesterday because I forgot my password, so I had to do a clean Rock install. Now when I try to run the update to go from 4.1 I get an error about NuGet access denied: I installed 2012 R2 and the full MS SQL Server. Any idea how to fix this? I tried to installed do a fresh NuGet install but thats not helping either.

0
- David Leigh replied 8 Years Ago
From what I can see of the error, this looks like it might be caused by file system permissions.
As a first step, make sure that whatever account is running IIS also has access to the directory mentioned in the error (C:\Windows\system32\...).

If you need further help, you'll need to post the full error details, which should be available here: "Home / System Settings / Exception List".
Edit Answer

From what I can see of the error, this looks like it might be caused by file system permissions. As a first step, make sure that whatever account is running IIS also has access to the directory mentioned in the error (C:\Windows\system32\...). If you need further help, you'll need to post the full error details, which should be available here: "Home / System Settings / Exception List".
From what I can see of the error, this looks like it might be caused by file system permissions. As a first step, make sure that whatever account is running IIS also has access to the directory mentioned in the error (C:\Windows\system32\...). If you need further help, you'll need to post the full error details, which should be available here: "Home / System Settings / Exception List".
From what I can see of the error, this looks like it might be caused by file system permissions. As a first step, make sure that whatever account is running IIS also has access to the directory mentioned in the error (C:\Windows\system32\...). If you need further help, you'll need to post the full error details, which should be available here: "Home / System Settings / Exception List".
Save Cancel
0
- Jay Greentree replied 8 Years Ago
I ended up doing a clean install because the nuget directory did not exist.
Edit Answer

I ended up doing a clean install because the nuget directory did not exist.
I ended up doing a clean install because the nuget directory did not exist.
I ended up doing a clean install because the nuget directory did not exist.
Save Cancel
David Leigh

8 years ago

And did that fix the problem?
0
- Jay Greentree replied 8 Years Ago
Reinstalling Server 2012 and SQL Server resolved the issue not sure what the problem was but I'm just glad it was my local server and not the production server.
Edit Answer

Reinstalling Server 2012 and SQL Server resolved the issue not sure what the problem was but I'm just glad it was my local server and not the production server.  
Reinstalling Server 2012 and SQL Server resolved the issue not sure what the problem was but I'm just glad it was my local server and not the production server.  
Reinstalling Server 2012 and SQL Server resolved the issue not sure what the problem was but I'm just glad it was my local server and not the production server.  
Save Cancel