When you run a full content deployment job to deploy content from a source site to a destination site in Microsoft Office SharePoint Server 2007, the following error messages are logged in the Application log:

• Event Type: Error
  Event Source: Office SharePoint Server
  Event Category: Content Deployment
  Event ID: 5326
  Date: 8.11.2007
  Time: 22:19:34
  Description: Failed export operation for Content Deployment job 'Update deployment'. Exception was: 'Microsoft.SharePoint.SPException: The changeToken refers to a time before the start of the current change log. at Microsoft.SharePoint.Deployment.SPExport.ThrowInvalidChangeTokenError(DateTime minChangeTime, Int32 minChangeNumber) at Microsoft.SharePoint.Deployment.SPExport.GetIncrementalChanges() at Microsoft.SharePoint.Deployment.SPExport.CalculateObjectsToExport() at Microsoft.SharePoint.Deployment.SPExport.Run() at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoServerToServer ()'

• Event Type: Error
  Event Source: Office SharePoint Server
  Event Category: Content Deployment
  Event ID: 4958
  Date: 8.11.2007
  Time: 22:19:35
  Description: Publishing: Content deployment job failed. Error: 'Microsoft.SharePoint.SPException: The changeToken refers to a time before the start of the current change log. at Microsoft.SharePoint.Deployment.SPExport.ThrowInvalidChangeTokenError(DateTime minChangeTime, Int32 minChangeNumber) at Microsoft.SharePoint.Deployment.SPExport.GetIncrementalChanges() at Microsoft.SharePoint.Deployment.SPExport.CalculateObjectsToExport() at Microsoft.SharePoint.Deployment.SPExport.Run() at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoServerToServer () at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.ExecuteJob() at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean runAsynchronously)'

Additionally, a content deployment job process may not remove content from the destination server after the content is removed on the source server.

This issue may occur if the time zones are set incorrectly for the destination and source servers.

To resolve this issue, set the correct time in the source and destination servers. You must set the following:

• You must set the local time zone, the date, and the time on the source and destination servers.
• You must set the time zone on the Web Application General Settings page in Central Administration.
• You must set the time zone of the source and destination site collections. You can do this by running the following command:
  stsadm -o setproperty -pn defaulttimezone -url URL of the site collection -pv CodeFromTimeZonesTable
  In this command, the CodeFromTimeZonesTable placeholder represents code from a Time Zones tabe on the Microsoft TechNet Web site. To view this Time Zones table, visit the following Microsoft TechNet Web site:
  http://technet.microsoft.com/en-us/library/cc287874.aspx (http://technet.microsoft.com/en-us/library/cc287874.aspx)

If this issue is still not resolved, use the following methods in the order in which they are presented. Determine whether the issue is resolved after you apply each method.

Method 1

Run the full content deployment job from the source server to a test site collection in the source farm before you deploy content on the destination server.

Method 2

Run a new content deployment job. To do this, follow these steps:

1. Create a new Web application that contains a site collection by using the Blank Site template.
2. Create a new path and a new job for content deployment.
3. Verify that the issue does not occur when you run the new content deployment job.

Method 3

Use the Stsadm command-line tool to export the content from the source site and then import the content to the destination site.