Access Denied Error when Updating a Solution 

Tags: SharePoint Development

Ever get an "Access to the path c:\... is denied" error when try to deploy or upgrade a SharePoint solution package? I've been getting this error intermittently over the past couple weeks and just today I figured out why! It wasn't rocket science to figure out – but the removal of one less annoying thing in my life is always worth celebrating…

 

Here were the errors I was getting:

 

 

 

For me anyways, the problem is because I haven't been disciplined with using my solution packages. Sometimes I would deploy/upgrade the solutions, and sometimes I would do it manually. NOT GOOD! When using solutions – don't cheat or be lazy by manually deploying stuff! Always use STSADM. Otherwise your solutions will stop working. Bad Phil, bad!

 

Anyways, here are the steps I took to fix this access denied error and get my solutions up and running again:

 

  1. Delete the file(s) off the file system on all web front ends where you're getting the error – in my case, I'm going to delete the ControllerCPU.aspx file.

  2. Using STSADM, run the deploysolution command and specify "force":




  3. The solution should now be successfully deployed:




  4. (optional) – if you had intended on doing an upgrade to an existing solution, you should now re-run the upgradesolution command again to be safe, just incase if in step 3 you deployed the old solution and not the new one:


 

Phil

 
Posted by Phillip S. Wicklund on 8-Oct-08
2  Comments  |  Trackback Url  | 0  Link to this post | Bookmark this post with:        
 
Failed to render control: Value does not fall within the expected range.

Comments


Matt Connollycommented onMonday, 13-Oct-2008
Why do you say to always use STSADMN? Why shouldn't deploying from Visual Studio always work? I have run into this problem myself recently as I've been getting started with a project, and restarting IIS seems to take care of it. For some reason I can't even navigate to the folder with the custom control inside Windows Explorer- I get a "location not found" / "access denied", even though I'm an Administrator on the box.

Phil Wicklundcommented onWednesday, 12-Nov-2008
Matt - "always" was too sweeping, as you mentioned. You can use VS to update/deploy solution packages, I just prefer to do it manually. In which case, I'm not sure about the issue you're faced with...
Name:
URL:
Email:
Comments: