Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Content deployment job not working after Moss dec 2009 CU Update

  Asked By: Norma    Date: Apr 15    Category: MOSS    Views: 1492

We have configured a content deployment job on our server farm. Which takes
the content from the source Site collection and migrates the contents to
different site collection on a different farm. The job is not working now
after the Moss Dec2009 CU updates.

The job gets struck showing the job status as “Preparing”.

We had checked the Moss log files for errors we are getting the following
error on Moss log files:

05/12/2010 12:08:39.88 w3wp.exe (0x0290)
0x1EDC CMS Content Deployment
78cf High Content Deployment Status is not available

Share: 

 

1 Answer Found

 
Answer #1    Answered By: Ruth George     Answered On: Apr 15

Sometimes when timer service is not able to start the time job  for content  
deployment, this might happen.

You can try following action:

1. Restart Timer Service through Service.msc on source farm.

If the operation times out then increase timeout for windows services as
follows:

Regedit
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.

String Value: WaitToKillServiceTimeout
Value Data: 60000

Create DWORD value at same location:

DWORD Value: ServicePipeTimeout
Value Data: 60000

2. Clear configuration cache as per instruction mentioned in KB 939308
(Error message mentioned in this KB is different but the resolution section
applies here )

3. Delete the Content deployment  Path and Job in question and recreate them.

4. You can see if this is becasue of timer job or not. Just run STSADM
export of the source site.

 




Tagged: