Thanks Wyatt, I think the problem is with the client's system. I know that it is down to them to fix it, but just in case they ask, is it possible for us to relax this requirement, by increasing the 5 minute limit?
One of our customers is getting this error occassionally. I'm not sure if the time is wrong on his client machines or on the TFS server that we host for him. What is the allowable time discrepancy between the systems?
/*
MessageId: TF_E_WRONG_TIME
Message code (in Hex): 0x7
Message code (in Decimal): 7
MessageText:
This computer's system time is more than 5 minutes (before/after)
different from the TurboFloat Server's system time. Make sure
the server's Date, Time, and Timezone are set correctly and make
sure this computer's Date, Time, and Timezone are set correctly.
Note: That TurboFloat and TurboFloat Server work even if the timezones
of the computer/server are different. In other words, your
TurboFloat Server could be hosted in France and have a "client"
computer running in New York (a 6 hour time difference) and
everything will work fine provided both server and computer
have their date, time, and timzones correctly configured.
*/
#define TF_E_WRONG_TIME ((HRESULT)0x00000007L)
From TurboFloat.h.
Thanks Wyatt, I think the problem is with the client's system. I know that it is down to them to fix it, but just in case they ask, is it possible for us to relax this requirement, by increasing the 5 minute limit?
I know that it is down to them to fix it, but just in case they ask, is it possible for us to relax this requirement, by increasing the 5 minute limit?
Nope.
Just have them sync their time with a known good timeserver. Then they'll be set for decades to come. (The time drift even from junk computers can be measured in seconds over the course of years).