SharePoint 2016, Sharepoint 2013, Sharepoint 2010, Windows Server 2012, Sql Server 2012,2014,IIS, Active Directory,User Profile Service, Managed MetaData Service, Search Service, Topology, Web Application, IIS, Site collection, List, Library, PowerShell, office web app, Windows Authentication, NTLM, Kerberos, Saml, ADFS, Active Directory Import, MIM, Content Deployment Stuck in running phase – SharePoint

Content Deployment Stuck in running phase

Content Deployment Stuck in Running phase or in ‘Cancel Pending’ phase for an unreasonably long time.
Export Logs show ‘Calculating objects to export’ and nothing after that.

Unknown. Usually happens when there is a large amount of content being deployed.


To resolve this issue, we have to first cancel the Content Deployment job. Chances are that it will stuck again in ‘Cancel Pending’ status for a long time.  So the timer job associated with the job has to be killed.

Restart the SharePoint 2010 Timer services from Services Console at the source farm App server, if still its stuck at exporting phase.

Here are the steps to successfully cancel/stop a content deployment job.

Step 1: Deleting the Timer Job

On the Central Admin Server, run the Powershell Commands

# Find the exact “Name” of the Content Deployment timer job (This may not be the same as display name in CA).

$job = Get-SPTimerJob <NameOf TimerJob>

Step 2: Recycle the Timer Service

Get-Process owstimer | Stop-Process
# by killing “owstimer” process you can avoid caching of “Job Definitions” you just deleted and don’t worry, it’ll start automatically in a few seconds

Step 3: Force Fail the Content Deployment Job

1) Go to Central Admin -> SiteActions -> View all Site Content -> ‘Content Deployment Jobs’ List

2) Select the Content Deployment Job and click ‘Edit Item’

3) Change the ‘Last Status’ parameter to ‘2’ (2 is equivalent to failure)

The following options will be blank but are required to be able to save it.
RemoteJobDestinationServerUrl  <CA address>
    RemoteJobDestinationSiteCollection  <destination address>
    RemoteJobIncludeSecurity 1
    RemoteJobIncludeUserInfoDateTime 1

4) Save it
The status of the job now show as Failed.
Step 4: Click ‘Run Now’ on the Content Deployment Job

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *