My Quick Deploy Job is causing 4958 and 6398 errors in the application log every 15 minutes


The SharePoint Content deployment topic has been well documented, but I recently ran into an issue which, I was surprised to find, was not covered.

In SharePoint 2007, when you set up a new Content Deployment Path, you automatically get a new job named “Quick Deploy job for Path ‘<your Path name>’

This job is designed to be used by content publishers of the source site, by using the Quick deploy option from a page that has been published (major version).  Publishers access this option via:

Site Actions -> Show Page Editing Toolbar -> Tools -> Quick Deploy


Before your publishers can use this option, you must enable the quick deploy job.  To do so, you would click the dropdown on the Quick Deploy job -> click Quick Deploy Settings -> Check the box [x] Allow Quick Deploy jobs along this path -> then click on Specify Quick Deploy Users

This will allow you to add users to the Quick Deploy Users [Limited Access] group on the site collection designated in the Deployment Path.  Once you have done this, the Tools -> Quick Deploy option on a published page will no longer be greyed out for that user.

However, if no contributors have clicked Tools -> Quick Deploy, you will notice that the Job status in central administration shows the following for Last Run: Not Yet Run


You will also see the following errors in the application log each time the scheduled Quick Deploy Job is scheduled to run:

Log Name:      Application
Source:        Office SharePoint Server
Event ID:      4958
Task Category: Content Deployment
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <SharePoint Server Name>
Publishing: Content deployment job failed. Error: 'System.ArgumentOutOfRangeException: ContentDeploymentJobReport with ID '{00000000-0000-0000-0000-000000000000}' was not found.
Parameter name: jobReportId
   at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobReport.GetInstance(Guid jobReportId)
   at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.get_LastReport()
   at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.get_SQMDeploymentJobFlags()
   at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.CollectSQMData()
   at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean runAsynchronously)
   at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition.Execute(Guid targetInstanceId)'

Log Name:      Application
Source:        Windows SharePoint Services 3
Event ID:      6398
Task Category: Timer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <SharePoint Server Name>
The Execute method of job definition Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition (ID a2a9517b-f1e5-4d5e-803d-1eaae55cd84c) threw an exception. More information is included below.

ContentDeploymentJobReport with ID '{00000000-0000-0000-0000-000000000000}' was not found.
Parameter name: jobReportId

NOTE: the (ID <GUID>) in this event will be the GUID of your Quick Deploy Timer Job, which is different than the GUID for the actual Quick Deploy Job object.

Item of Interest:
There is a list under your central administration site collection, located at http://<yourCentralAdminURL>/Lists/Content%20Deployment%20Jobs.
This list contains all of your content deployment job definitions.
Drop down on the Quick Deploy job for Path ‘your path’ -> View Item
You can use these properties to positively match the job with the GUID reported in the error, which will be shown under TimerJobId.
You will notice that the value for LastReportId is empty.

 So, how do I fix this?  Have a publisher quick deploy something in the affected Site collection, and voila, no more errors

Once a publisher who is a member of the Quick Deploy Users group uses the “quick deploy” option from the source site, the Quick Deploy job will complete successfully, and you will no longer see the errors.  The Quick Deploy job status in Central Administration will update to Succeeded.






Comments (0)

Skip to main content