Content Deployment Issues

We have been experiencing time out issue with content deployment after the Daylight Time changes on our servers and I wonder if any one has had the same problems.

The scheduled jobs export and on the import phase they get timed out.

Thanks

[249 byte] By [gatharia] at [2008-2-15]

«« Vertical Split Pane (not tab group)
»» SSIS access denied

# 1

We have run into the same issue since the W2k3 server DST patch. When starting a content deployment job, the job hangs in the preparing state. An hour later, the job either times out, or gives us an error message of

3/15/2007 11:10 AM
The changeToken refers to a time before the start of the current change log.

3/15/2007 11:10 AM
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()

3/15/2007 11:10 AM Content deployment job 'Deploy Report Site' failed.The exception thrown was 'Microsoft.SharePoint.SPException' : 'The changeToken refers to a time before the start of the current change log.'

If anyone has any idea or has a resolution, can you please respond.

Thanks,

Dan

DKeeling at 2007-9-12 >

top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Enterprise Content Management...

# 2

I am having this issue as well on multiple servers. I removed the DST patch on my test server and it fixed the problem. I re-applied the patch and it seems to be broken again.

Anyone out there know anything about this?

Rabbit

Rabbitrun at 2007-9-12 >

# 3

Found this from Microsoft KB:

http://support.microsoft.com/kb/932563/en-us

Rabbitrun at 2007-9-12 >

# 4

We were abl to resolve this by changing the server time to a non DTS zone, rebooting and then changing the server time back to the DTS time zone.

The only problem with this is that owstimer will go back to the earlier state (state after DTS install) is you reboot the server(s).

If you ever reboot your server, you have to repeat the work around.

Thanks

gatharia at 2007-9-12 >

# 5

That worked! Thanks for the tip Gatharia.

Does anyone have any idea if MS is working on an official fix for this -OR- will this issue go away once we roll past the old DST date which is coming up soon?

Rabbit

Rabbitrun at 2007-9-12 >

# 6

According to Microsoft the DST issue will not show after the old DTS times but in octomber expect that to come back if Micrsosoft has no OS patch. The crazy thing is that owstimer seems to have it's own clock other than the system clock. We had to enable verbose logging in sharepoint and read all logs to see what is happening. ( I heard that this time issue was a bug in windows 2000 but it is the same in windows 2003 too)

gatharia at 2007-9-12 >

# 7

I was wondering about that myself. It seems like the owstimer service doesn't get its time from the system clock. Very strange. It also looks like the fix you suggested worked yesterday but for some reason (and the server wasn't rebooted) Content Deployment is back to being broken again!

All this trouble because of stupid daylight saving time!!!

Rabbitrun at 2007-9-12 >

# 8

One more thing about the workaround is that this should be done on source and destination servers. If that is not so the export phase will work but the deployment will fail during the import phase. Also, if with of the serves is rebooted, deployments will still fail because owstimer will be out of phase again.

gatharia at 2007-9-12 >

SharePoint Products and Technologies

SharePoint - Enterprise Content Management

SharePoint Products and Technologies Hot Topic

SharePoint Products and Technologies New Topic

SharePoint Products and Technologies

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech