Proper stsadm commands to update SharePoint Solution/Feature?

The proper way is to use the -o upgradesolution command. In most cases there is no need to retract and delete the solution and reinstall it. Be sure and follow it up with an -o execadmsvcjobs as usual.

Up vote 4 down vote favorite 3 share g+ share fb share tw.

What are the proper stsadm commands in sequence to force an upgrade to a SharePoint solution. I have tried C:>"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm. Exe" -o deploysolution -name "MySolution.

Wsp" -immediate -allcontenturls -allowGacDeployment -allowCasPolicies -force followed by C:>"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm. Exe" -o execadmsvcjobs It seems to deploy and shows the solution as having a deployment time of when I push these commands but my files don't appear to get updated and new files don't appear. Am I missing something?

Do I need to do an IISReset /noforce after processing these commands. Thanks, Josh Lewis sharepoint solution stsadm feature-upgrade link|improve this question edited Apr 14 '09 at 16:06 asked Apr 14 '09 at 15:58Omenof53118 25% accept rate.

Stsadm -o retractsolution -name ... -immediate -allcontenturls stsadm -o execadmsvcjobs stsadm -o deletesolution -name ... stsadm -o addsolution -filename ... stsadm -o deploysolution -name ... -immediate -allcontenturls -allowgacdeployment -allowcaspolicies stsadm -o execadmsvcjobs A few warnings: Sometimes you have to start with deactivating the feature first (stsadm -o deactivatefeature). When I changed a Site feature containing a list template to a Web feature I ended up with double links on the create page. So I had to install the old feature again, deactivate it and then reinstall the new feature.

Do NOT use -force if you're not sure what you are doing. If you use it with the -o deletesolution command you may end up with old versions of files on some or all of your servers. Such problems can be hard to track down and it gives you a lot of extra work, especially if you have multiple front end servers.

Ghosted files don't get updated. Stsadm -o execadmsvcjobs will proces any job, that is late on processing reactivate features, Those that contain content (next time; use feature stapling! ) upgrading solutions will not always automatically install new features (yes, install, not activate).

Check this.

An IISRESET might also be worthwhile but you could try to run the "SharePoint Products and Technologies Configuration Wizard", AKA PSCONFIG. EXE Located at C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN It'll syncronize the informations that are on the Database, the IIS and the Binaries. It's necessary to run it when you apply a Service Pack.

Also make sure that all servers on your farm has access to the Central Administration and that you ran the PSCONFIG on all of them.

I think because you are supplying the -force parameter in the deploysolution command you are actually suppressing the error message that would probably be displayed - along the lines of Solution already exists. As stated previously either do retract->deploy or upgrade (depending on your scenario).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.