Home Library Wiki Learn Downloads Support Forums Blogs
Sign in | United States - English | |

Syncsolution: Stsadm operation (Office SharePoint Server)

Updated: April 26, 2007

Applies To: Office SharePoint Server 2007

Updated: 2007-04-26

Operation name: Syncsolution

Performs a synchronization of the Windows SharePoint Services Solution Package (WSP) solutions stored in the configuration database with the files stored on disk. The .wsp files will be synchronized in the order in which they were submitted to the server.

Note Note:

It is not possible to remotely synchronize a computer.

Syntax

stsadm -o syncsolution

   -name <name>]

   [-lcid <language>]

   [-alllcids]

stsadm -o syncsolution

   -allsolutions

Parameters

Parameter

Value

Required?

Description

name

A valid name of a solution, such as “SampleSolution1”

Yes

Forcibly resynchronizes a particular solution. Any files previously written in a solution will be erased, and the solution’s files in SolutionCache will be erased. The files will be recopied from the server, expanded, and then redeployed.

lcid

A valid locale ID, such as "1033" for English

No

Language locale ID for the solution

allcids

<none>

No

Specifies that all language packs for all locale IDs are deployed along with the solution.

allsolutions

<none>

Yes

Resynchronizes all .wsp files in the solution store to the server. Files that have been deployed via the solution infrastructure will be removed from the global assembly cache, vserver bin, _layouts, and SolutionCache folders on the computer. The .wsp files for the server will be recopied, expanded, and then redeployed.
Community Content Add
Annotations FAQ
Does it actually work?

You have already tried deactivating features, retracted the solution and redeployed, nothing happens, the database completely ignores your changes.

What do you do?

You look through the vast operations in stsadm and you find... syncsolution!

But no, I've tried this operation on different occasion, and I've never ever seen it work.

When I find myself in the situation discribed above I ussually have to nuke the webapplication and redeploy everything or make new instances (new GUID, names , etc) of the stuff that won't upgrade.

Is this command any good? Anyone used it succesfully?

History