Tag Info

Hot answers tagged

9

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


9

Central Admin - System Settings - Manage Farm Solutions, pick your wsp and hit Retract, then Remove once it's done.


5

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


5

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


5

Check if your Windows SharePoint Services Administration and Windows SharePoint Services Timer jobs are running. Also after ensuring, run this command stsadm -o execadmsvcjobs


5

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


4

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


2

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.


2

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


2

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


2

There is an event handler on the feature that is triggered on deactivate, which you could remove lists then. But that would require the features to be deactivated before retraction.


1

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


1

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


1

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


1

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


1

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


1

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.


1

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


1

Just try this command in SharePoint Management Shell stsadm -o execadmsvcjobs


1

I had this issue today - if the 10050 Type is a custom list definition that you have created then this behavior is by design. The list definition will get removed and therefore the list instance will fail because the definition it inherits from is no longer present. If you redeploy the solution again you will notice that the list instance returns and no ...


1

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: // This folder is physically located in this global location: C:\Program Files\Common Files\Microsoft Shared\web ...


1

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 Remove-SPSolution YourSolutionName.wsp


1

Monica, 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: http://www.alexthissen.nl/blogs/main/archive/2007/07/18/removing-malfunctioning-windows-sharepoint-services-solutions.aspx Caveat: I don't THINK that SP2010 has changed the STSADM commands that ...


1

That would retract the solution from all Web Front End servers. It does this via a timer job. Sharepoint also waits until the solution is retracted from all web servers before it shows the solution as "Retracted" in the central admin. We had a situation where it used to fail on one server or another but we later found that IIS on the failing server itself ...


1

Bad luck on the WSPBuilder vs WSeWSS decision! I think the main thing to consider here is that feature deactivation does not fire automatically when solutions are retracted. So maybe what you need to ensure is that features are deactivated (manually or via a script) in the correct sequence before your WSPs get retracted. This should then provide you with ...



Only top voted, non community-wiki answers of a minimum length are eligible