Retracting sharepoint webpart - dll is in use errors

Here's the situation:

I deployed a demo version of a sharepoint webpart as a solution to my webserver before i deployed the full version. So i deploy it, added it to a webpage and tried it out. Afterwards i removed it from the webpage, and deactivated the solution, then retracted the solution.

Now is where the trouble came in at: I went to go deploy the full version of it and i got a "dll is in use error".

All attempts to remove this dll i got errors, and crashed the server a few times during the proccess as well. Fun stuff.

The solution:

The solution is remarkably simple that most people will look right over it:

Go to the webpart galery for the site(s) you used the webpart on, and remove it from the gallery. After doing this (and making sure it wasn't on any of the other pages on the site) deploying the package went through with out a problem. Wish this was documented better (and the solution providor knew about it more).

Comments

Post a Comment

Popular posts from this blog

CI Build broke after nugit update

One of those moments where your heart drops : Your using CI on a remote hosting service (like AppHarbor) and your build fails. You look into the fail reason and find out it is because you updated the packages in your build. Wait, my update from nuGet broke everything?! Wtf?! The error looks something like this, putting it in here for search engine's : Build started 6/10/2013 12:30:20 AM. 1>Project "D:\temp\xly5bsff.qvp\input\.sln" on node 1 (default targets). 1>ValidateSolutionConfiguration: Building solution configuration "Release|Any CPU". 1>Project "D:\temp\xly5bsff.qvp\input\.sln" (1) is building "D:\temp\xly5bsff.qvp\input\\.csproj" (2) on node 1 (default targets). 2>D:\temp\xly5bsff.qvp\input\\.csproj(880,3): error MSB4019: The imported project "D:\temp\xly5bsff.qvp\input\packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets" was not found. Confirm that the path in th
Read more

Sharepoint 2007 - Access Denied when you try to edit

I'v had this solution for a little while now but never wrote it down anywhere for people to see. Here is the situation: In a site collection, you make a new list/document library in any sub-site or the main website. You then add a new item/document to the folder, and then attempt to edit the item You then see something along the lines of "Access Denied" , even if you are on the system account. This happens with every new list you create on any site or subsite. Your problem is a corrupted field definition at the site collection level. Specifically the "Effective Permissions Mask" is missing an attribute in it's xml scheme - RenderXMLUsingPattern="TRUE" The fix comes in 3 steps: 1. Update your server to the most recent cumulative update package (Service pack 2 or greater). You can get more information about this from the Sharepoint team blog post on SP2 . Included in SP2 is a hotfix that prevents this from occurring ever again on any other site co
Read more

Project 2010 and Project Pro 2007

Just a FYI since no one knew this from what i can tell already: If you are enabling BCM (Backwards Compatibility Mode) for project 2007 to connect to Project Server 2010, there are a few things you should know first. Right off the bat, clients have to be updated to Service Pack 2 . Next, when your setting up your project server, Note this key fact I could not find anywhere, and did not get hint about in the technet forms when i posted about my problems: You CAN NOT use Claims based authentication on your web application that is hosting Project Server 2010. The 2007 Client will not connect to the server. The 2010 client will connect with no problems. Quick and dirty, hope that helps everyone!
Read more