No, they are seeing this issue come up randomly: Exception Message: TF54000: Cannot update data because the server clock may have been set incorrectly. Contact your Team Foundation Server Administrator. (type DatetimeShiftDetectedException)
. but there is no obvious problems with the date times in the changesets and pending changes related tables (as far as I can see with a quick SELECT FROM ORDER BY) Given that sharepoint and reporting services are also not working and they also don't have a reliable backup system (there snapshot got deleted) AND they want to go from 05 to 08, then we're tackling it all in one go by doing a clean install so that we have a known safe starting point. The loss of datetimes in the checkins is an acceptable loss, however I'm trying my best to get the comment field updated. A quick review of the database shows that I can probably safely do a simply update on the tbl_changeset table, since this contains the checkin date as well as the comment. Naturally I will do a couple practice runs on the TFS08 VPC. But can anyone see any other potential issues with this? Thanks, Steve From: [email protected] [mailto:[email protected]] On Behalf Of Mitch Denny Sent: Thursday, 18 December 2008 8:47 AM To: [email protected] Subject: RE: TFS Upgrade - Update timestamp in comments What do you mean about bad data around check-ins? Has someone manually edited the database? Mitch Denny | Principal Consultant | Readify Pty Ltd | M: +61 (0)414 610 141 [cid:[email protected]]<http://readify.net/about-readify/press/readify-makes-2008-mis-strategic-100-list/> From: [email protected] [mailto:[email protected]] On Behalf Of Steven Nagy Sent: Thursday, 18 December 2008 7:23 AM To: [email protected] Subject: RE: TFS Upgrade - Update timestamp in comments Grant: The destination is completely blank: fresh install of TFS08 We ruled out a backup/restore scenario because there is possibly some bad data around checkin times. We actually want the dates flattened, but still want the original date appended to the comments field for reference just in case. We want all 4 projects migrated in this way (ie the whole TFS). The good news is that the client isn't using WSS or RS so we have some flexibility on how we go about this problem. This is why I chose the TFS to Tfs migration tool. Mitch: Unfortunately I don't think I'll have time for dev to get this done. We are doing a dry run tonight and then the official migration on Saturday. From: [email protected] [mailto:[email protected]] On Behalf Of Grant Holliday Sent: Wednesday, 17 December 2008 8:00 PM To: [email protected] Subject: RE: TFS Upgrade - Update timestamp in comments Does the destination have any other content? Is it an option to copy the whole databases and destroy the other three projects? (If you do this, don't forget to change the server guid using TfsInstanceInfo.exe. Search my blog for it) There are some well known limitations of the TFS-TFS Migration Tool + toolkit. I encourage you to checkout the wiki on codeplex for common/recommended/not recommended scenarios. The good news is that we are working on the sync tool and should have some more exciting news about it later next year. Regards, Grant ________________________________ From: Mitch Denny <[email protected]> Sent: Wednesday, December 17, 2008 1:20 AM To: [email protected] <[email protected]> Subject: RE: TFS Upgrade - Update timestamp in comments Take a look at this: http://www.codeplex.com/MigrationSyncToolkit You will need to do some dev... Mitch Denny | Principal Consultant | Readify Pty Ltd | M: +61 (0)414 610 141 [cid:[email protected]]<http://readify.net/about-readify/press/readify-makes-2008-mis-strategic-100-list/> From: [email protected] [mailto:[email protected]] On Behalf Of Steven Nagy Sent: Wednesday, 17 December 2008 9:58 AM To: [email protected] Subject: TFS Upgrade - Update timestamp in comments Team, We're looking at using the TFS to TFS migration tool to move source history for one TFS (4 projects) to another. I'm aware that the timestamps for the new items will be the day of the migration. However it would be nice to store the existing timestamps in the comments field or something similar before the migration. Any ideas how this could be achieved? Obviously an SQL update statement could be constructed, but I live in fear of touching the database! Cheers, Steve ________________________________ List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists ________________________________ List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists ________________________________ List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists ________________________________ List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists ________________________________ List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists -------------------------------------------------------------------------------- List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists
<<inline: image001.jpg>>
