RSS Feed Feed your read!

Bookmark and Share







Tag Cloud

ASP.NET Generic, Best Practices, Business Intelligence, Freeware Releases, InfoPath, Infrastructure, jQuery, Lunch & Learn Events, Project Server, Random, Reporting Services, Search, SharePoint Administration, SharePoint Business Analysis and Project Management, SharePoint Development, Silverlight, Social Networking, Speaking Events, White Paper Releases, Workflow Foundation,

Archives

June 2007 (3)
August 2007 (1)
November 2007 (2)
February 2008 (2)
April 2008 (5)
May 2008 (7)
June 2008 (8)
July 2008 (7)
August 2008 (3)
September 2008 (7)
October 2008 (1)
November 2008 (3)
December 2008 (3)
January 2009 (7)
February 2009 (5)
March 2009 (10)
April 2009 (2)
May 2009 (6)
June 2009 (3)
July 2009 (4)
August 2009 (6)
September 2009 (3)
October 2009 (9)
November 2009 (10)
December 2009 (1)
January 2010 (1)
February 2010 (3)
March 2010 (6)
April 2010 (2)
May 2010 (3)
June 2010 (4)
July 2010 (3)

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...

Bookmark and Share

Note: Facebook no longer sends notifications for comments, so it may be a number of days before I see your post. For urgent matters, click "Contact Me" on the top nav. More info: Click Here.