Thursday 23 July 2009

ContentDeploymentJobReport with ID '{e379594a-a267-4dfc-ae37-70f8f392798c}' was not found - Event ID: 4958

The Problem
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.

In the SharePoint Logs I found:

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
C
ritical 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)'

This error always occurred with the same GUID. The error occurred every 15 minutes. This was actually the time the Quick Deployment Job was running. When I tried to open the history of the Quick Deployment Job, the error page below was displayed.









Then, when I was looking at the Deployment list: (<your site>/Quick Deploy Items/AllItems.aspx)














The attempts
I deleted all items, but it didn't work. Another side effect of what I did was that I couldn't test if the Quick Deployment Job worked or not, because it needed at least one item to start the task. As such, I recovered the items from the Recycling Bin.

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.

The Solution
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.

A downside to this solution is that I had to run a full deployment again, because all file GUIDs weren't matching. But that wasn't a big problem, because that seems to happen quite frequently with Sharepoint.

No comments:

Post a Comment