IsActivated question

Wyatt,Here is a scenario...Install and activate on Machine-A. Clone to identical Machine-B. What should the return value of IsActivated() be on Machine-B? Do you re-ID the machine to determine that it not the same machine?

Thx,John

Yes, the machine is re-IDed every time IsActivated() is called. In other words, a cloned Machine-A installed on Machine-B will return "not activated" when the software is run.

Another question about IsActivate.....

I want to see if this is a known issue and I'm not chasing a red-herring:I have zero Grace Period. The key gets activated at install time. After installation, I use Activate() at boot time. If it fails with a network failure, I do an IsActivated.Can Activate() ever something other than TA_OK or TA_E_INET with an activated key (aside from TA_INUSE or TA_REVOKE) ?Can IsActivated() ever return something other than TA_OK for again an activated key?

Thx,John

Hey John,

The current return codes for Activate() are the following:

  • TA_E_PKEY (i.e. you didn't save the product key before calling Activate())
  • TA_E_INET
  • TA_E_INUSE
  • TA_E_REVOKED
  • TA_E_PDETS (the TurboActivate.dat file can't be found or failed to load)
  • TA_E_COM (this rarely happens -- if you don't see this when you're designing your app on your development machine, you'll never see this error)
  • TA_E_EXPIRED (the user messed with their date/time settings -- tell them to fix it)
  • TA_FAIL (general failure)
  • TA_OK (everything worked fine -- they activated and it succeeded)

IsActivated has fewer return codes:

  • TA_OK (is activated)
  • TA_FAIL (is not)
  • TA_E_GUID (the GUID doesn't match)
  • TA_E_PDETS (the TurboActivate.dat file can't be found or failed to load)
  • TA_E_COM (same as above)

Of course, for both of these functions you should handle any unknown return codes as errors too.

Reply
Discard post