When you deploy a solution with a WebPart it deploys three things:
The dll with the web part
A SafeControl entry to be inserted into web.config
A .webpart (or .dwp) file with configuration settings to be inserted into the Web Part Gallery (this part actually happend at feature activation not at solution deploy, but..)
When you're adding a web part to a ...
Follow the steps for STSADM:
Open command prompt and navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
Use the stsadm command = stsadm -o retractsolution -name solutionName.wsp -immediate
and then remove the wsp = stsadm -o deletesolution -name solutionName.wsp
Follow the steps for Powershell:
Go to All Programs => ...
To fully remove it you have to maunally delete the .webpart or .dwp file from the wp gallery manually.
Go to [site]/_catalogs/wp/Forms/AllItems.aspx and you will see all of the webparts.
You might also like to check this post out
By the way, I normally deploy webparts as solution files and if i want to remove them, I retract them from Central Admin > ...
It is by-design that retract doesn't remove actual data. There is no event handler either that you could use to remove content after solution has been retracted. :(
I guess you would need to create custom functionality that will clear old content and run it after retracting solution.
Would it be possible to use site collections for this, and then just ...
Some notes that may help here:
A solution is first added (installed) and then deployed.
To remove a solution, you must first retract it, and then uninstall it.
A solution can be deployed either globaly or on a Web app basis (depending on its content, so it's not your call, but an inherent property of the WSP).
If you retract a solution deployed on a Web ...
Retract Solution fires off the Uninstall process of the WSP package from the farm. It's equivalent to the Uninstall-SPSolution PowerShell command and the opposite of the Install-SPSolution command.
Remove Solution is the equivalent of the Remove-SPSolution PowerShell command and is the opposite of the Add-SPSolution command. It can be seen as deleting the ...
There is no "cancel" method on SPSolution's.
If you still have the solution file(s) you can just add the solution again and re-i stall it. First you should start timer job and finish the retraction, and remove solutions though...
If your in 2010, you may as well start getting used to Powershell. Open up the SharePoint Management Console and run:
Uninstall-SPSolution YourSolutionName.wsp –AllWebApplications
Solution from Kai (slightly amended):
Eventually I had to reinstall WSS3. It seems the problem occurred because I changed the user accounts the Admin and Timer services ran under from those originally configured during installation.
You have to use STSADM commands to remove a stubborn solution. I have been in this situation several times in SP2007. This blog post covers all the steps.
Caveat: I don't THINK that SP2010 has changed the STSADM commands that much, so it should still work in SP2010. Let us know.
Just run below steps:
Run stsadm -o enumdeployments command in SharePoint Management
Look for the JobId string corresponding to your solution. Copy that string.
Run stsadm -o canceldeployment -id "you job id string here"
Your solution wsp will be in Not Deployed state. Now you can easily remove that solution using PowerShell Remove-SPSolution ...
Did you just add your permissions to the database or have they been there a while?
Try cancelling the deployment ( stsadm -o canceldeployment -id daa0d839-af5a-401b-baa4-7bbda2d3f2b3 ), then restart the timer service on all machines in the farm before trying again.
I've had issues in the past where updates to database permissions haven't quite worked until ...
Upgrading won't recreate your content types, since they're already created. You need to handle the version of the deployed content types in your code, and modify the content type accordingly based on what version is currently deployed. Jeremy Thake has a great blog post on using versioning with feature development.
Additionally, STSADM is deprecated--you ...
By default, you should see a Deployment Conflicts dialog box when you redeploy your solution to your development computer; this should have warned you that your existing list instance would be overwritten. To change this behavior, select the List Instance in Solution Explorer, and then change the Deployment Conflict Resolution property (in the Properties ...
I have faced a similar issue couple of days back. For couple of reasons the related DLLs will not be un-installed from GAC.
I deleted the solution respective DLLs from the GAC forcefully followed by an IIS Reset. It worked for me, Hopefully that's the solution for your scenario.
You need to update the add-in instead of deploying it again, to not lose your changes.
Follow below links for more info:
Update add-in web components
Update host web components
Also, if you are using sharepoint hosted add-in, you can use Fast Deploy to deploy files like JS and CSS.
I'd had a similar idea to @RJ Cuthbertson's answer regarding the GAC, but it would not let me uninstall anything from there. Until I found this:
IMPORTANT! Never ever do this on a production system, and always turn it back on afterwards.
Open Local Security Policy MMC
Goto Security Settings -> Local Policies -> Security Options
Locate "User Account Control:...
Have you tried commenting out the offending code, rebuilding/repackaging, and then running an Update-SPSolution command?
The FeatureUninstalling event occurs on removal, and, I believe, it will not be called when upgrading (that's what the FeatureUpgrading event is for).
If you can upgrade successfully and replace the offending code, you would then be able ...
You've hit the answer yourself. Be sure to deactivate any features before uninstalling/removing the solution. There are very few cases where it is appropriate to uninstall a solution before you've deactivated the feature. Be warned that if you uninstall the solution first you may not be able to deactivate the feature gracefully later.
Another possible ...
Is your STSADM command looks familiar to this one,
stsadm -o retractsolution -name mysolution.wsp -url http://www.mywebapplicaton.com -immediate
most people forget -immediate and then face random errors & exception.
on the page, click on the url where the webpart is and at the end put in "?contents=1" doing this should allow you to see the webpart that are still on the page, select the webpart and remove them. Then goto the webpart gallery and remove it. then retract the solution from sharepoint central admin.
now you can readd the webparts and features :)
Hope it ...
I'm assuming you are doing this in your 2007 environment before you upgrade. I'm not sure if there is an easier way such as quering the database or an stsadm command, but this should help.
This code will export the solutions installed in the farm as WSP files.
SPSolutionCollection solutions = SPFarm.Local.Solutions;
foreach (SPSolution solution in ...
According to: SharePoint v3 Localized Resources
If the assembly is deployed to the GAC, then the folder structure
containing the web parts resources will be in the virtual wpresources
folder and the folders will be named as follows:
folder is physically located in this global location: C:\Program
Files\Common Files\Microsoft Shared\web ...
Run SharePoint 2010 Management Shell as administrator and then run:
stsadm.exe -o execadmsvcjobs
It will manually trigger the administration jobs.