TA_E_EXPIRED returned from IsGenuine after successful activation

Hi there,

We're having an issue with calls to IsGenuine always returning TA_E_EXPIRED even after a call to Activate that has succeeded (and we can see the activation in the LimeLM dashboard).

Realize that this can happen when there is clock skew but our system is exactly on the world clock. This is currently occurring on two different Ubuntu VMs.

Happy to provide our account info / product id but I wasn't sure if the public forum was the appropriate place for this.

J.J.

Hey J.J.,

First, make sure you're using the latest TurboActivate (currently 3.4.2). If you're still getting that TA_E_EXPIRED from IsGenuine() after updating TA to the latest version, then there's something wrong with your date/time/timezone.

So here's the order of things to fix:

  1. Update to latest TurboActivate
  2. Fix the TimeZone is correct for the machine.
  3. Fix the Date of the machine.
  4. Fix the time of the machine.
  5. Restart the machine.

Hi Wyatt,

I tried again today and the issue no longer reproduces (not sure if something changed on your end to make it work). After this initial test I also upgraded to v3.4.2 and everything also appears to be working fine with that version.

Thanks very much for your assistance!

J.J.

I am seeing a similar issue on CentOS 5. The timezone, date, and time on the machine are all correct. I have tried it with both PDT and EDT timezones, and in either case I get this error:

Error activating product key: (13): The activation or trial extension has expired.

I appreciate any help you can provide in this regard.

Fereshteh

Did you do everything in the list in the order specified? Don't skip any steps.

  1. Update to latest TurboActivate
  2. Fix the TimeZone is correct for the machine.
  3. Fix the Date of the machine.
  4. Fix the time of the machine.
  5. Restart the machine.

I had restarted the machine, and everything (timezone, date, time) was correct. So didn't seem that I needed to restart again. But I did restart now without changing any of those, and that fixed the problem. Still not sure why needed to do that, but as long as it is working I am happy.

Thanks for the help,Fereshteh

We've just released TurboActivate 3.4.3. This should fix that problem.

Reply
Discard post