Hi, we use TA_IsDateValid to provide date limited licences, which usually works fine. Today we have a customer who is not able to use the product because TA_IsDateValid fails. They have told us that their PC clock time is set to UTC, could this be the reason? If so is there any workaround? The actual expiry date is in a couple of months so it's not a question of an hour or two here or there.
(In the meantime I'm trying to get some detailed logging from this user)
Messing with the date/time/time zone incorrectly will trigger TA’s fraud detection.
Tell them to fix their date, time, timezone, restart their computer, and you can send them a trial extension
Thanks, we're all sorted now, it turned out they were using the wrong key.
As a side note, setting the PC clock to UTC is a perfectly valid use case, this customer is on a boat offshore and everything runs by UTC. However the date check does seem to work correctly.
As a side note, setting the PC clock to UTC is a perfectly valid use case, this customer is on a boat offshore and everything runs by UTC.
Yep, when setting the time zone and date /time correctly everything will work (as you’ve seen).
However, when customers typically report this error they change one of the setting but not any of the others (meaning their time is invalid for “current time”).
We’ll probably write a FAQ on this because this comes up so often.
