Hi All -
Been using 4.2 and 4.1.1 with no real issues until recently. Suddenly, within the past few weeks, when a file is checked out, the checkout date/time reported on the screen and on the server are suddenly up to a couple weeks in the future, and the dates/times of files after "get" are incorrect - and curiously, seem to be the last time each file was modified in 2008. This has been happening for all of our 4.2 users, but NOT for those using the Microsoft client, which still functions just fine. No changes in the Linux environment, most of the machines have been running for months, and yes, the clocks on the client machines (and the VSS server) are correct. The "future checkout" times and dates reported by both clients are identical.
I have tried:
Closing/restarting SoS
Removing all files and doing "Get Latest Version"
Changing Tools->Options->File->Set date/time on local files... to all of the choices, with no effect.
The "future checkout problem" has been observed with both 4.2 and 4.1.1. The bogus checkout times are reported the same in 4.2, 4.1.1, and VSS (so they appear to be bogus in the database rather than just corrupted in the client.
Any help greatly appreciated! Thanks,
John
Bad file dates and checkout times in 4.2/4.1.1
Moderator: SourceGear
Re: Bad file dates and checkout times in 4.2/4.1.1
Never mind, we just discovered that the server end machine has some clock problems.
Re: Bad file dates and checkout times in 4.2/4.1.1
Thanks for the update.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Bad file dates and checkout times in 4.2/4.1.1
We've fixed the clock issue on the server - still having the problem that very old dates show up in the Remote Date field, which has really never been right. It turns out we only have one user using 4.2, the rest are for some reason using 4.1.1. Still investigating.