Runcontentdeploymentjob: Stsadm operation (Office SharePoint Server)

Applies To: Office SharePoint Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.

 

Topic Last Modified: 2016-11-14

Operation name: Runcontentdeploymentjob

Description

Runs a named deployment job. A job is associated with a path, and defines the specific content to be deployed from the source to the destination and the schedule on which the deployment should occur.

Important

This operation is case-sensitive. If you run the operation by using an uppercase "R", the following error message is displayed: "Windows SharePoint Services administration tool has encountered a problem and needs to close. We are sorry for the inconvenience."

Syntax

stsadm -o runcontentdeploymentjob

**   -jobname <name>**

**\[-wait\]**

**\[-deploysincetime\] \<date time\>**

Parameters

Parameter

Value

Required?

Description

jobname

A valid job name, such as "Job1"

Yes

Name of the deployment job

wait

Any one of the following values:

  • Yes

  • No

No

Specifies whether the command should return immediately (No), or wait until the job has completed running to return (Yes). The default setting is No.

deploysincetime

A valid date time format in the form: "mm/dd/yy hh:mm:ss"

No

Overrides the incremental changes, and forces it to use a specific date when you determined what incremental changes to export.

The DateTime value is based on the .NET System.DateTime structure. For more information about the .NET DateTime structure, see DateTime Constructor (https://go.microsoft.com/fwlink/?LinkId=87966&clcid=0x409).

If a time that is more recent than the last time of the deployment job, the following error message is displayed:

“The time specified in the -deploysincetime option is more recent than the last successful deployment time. This is not allowed since it will result in data-loss during this incremental deployment operation.”