Unfortunately there were several errors occurring on our source machine. These errors originated from the MOSS content deployment.
Event Type: Error
Event Source: Office
SharePoint Server
Event Category: Content Deployment
Event ID: 4958
Description:
Publishing: Content deployment job failed. Error: 'System.ArgumentOutOfRangeException:
ContentDeploymentJobReport with ID '{e379594a-a267-4dfc-ae37-70f8f392798c}' 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.EnsureLastReport()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean
runAsynchronously)'
For more information, see Help and Support
Center at http://go.microsoft.com/fwlink/events.asp.
07/01/2009 13:35:52.63 w3wp.exe (0x1120)
0x0958
CMS
Content Deployment 0 Unexpected
ContentDeploymentJobReport with ID '{e379594a-a267-4dfc-ae37-70f8f392798c}' was
not found in 'Job Reports' so throwing exception.07/01/2009 13:35:52.63 w3wp.exe (0x1120)
0x0958 CMS
Content Deployment 5ro8
Critical Publishing:
Content deployment job failed. Error: 'System.ArgumentOutOfRangeException:
ContentDeploymentJobReport with ID '{e379594a-a267-4dfc-ae37-70f8f392798c}' 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.EnsureLastReport()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean
runAsynchronously)'
I could not create a new path to the old location. This was because there could only be one path to one source-destination-pair. So this didn't work either.
To fix the problem I deleted the old paths and Deployment Jobs. I created a new path and new Deployment Jobs on our server and it worked.
No comments:
Post a Comment