TA_IsGenuineEx, Offline activation & TA_Fail

Hi,

did the following:- activated an license (online)- deactivated the license- disconnected from the internet- activated an license (offline method - using turboactivate.exe)- connected to the internet- disconnected from the internet- waited multiple days

in our code:- TA_IsGenuine returns TA_E_INET as expected- TA_IsGenuineEx returns TA_FAIL *not expected* (nDaysBetweenChecks = 1, nGraceDaysOnInetErr = 1, flags = TA_SKIP_OFFLINE) - TA_GenuineDays same params, returns TA_OK, daysRemaining = 0, inGracePeriod = 0

the weird thing is that I did this twice once on windows 7 and once on windows 8 and only the windows 7 one fails, under what circumstances can TA_IsGenuineEx return TA_FAIL?- while flags = TA_SKIP_OFFLINE- and offline activation is done

(we're using version 4.0.9.4, dll based, visual studio 2013 compiler, for reference the key I used to test this is E7G9-323P-MU9I-5CNE-7CZR-ERR9-5ATA)

First, before you do anything else, update TurboActivate to the latest version. My guess is that's the problem. If it doesn't solve the problem, we can at least continue on knowing that we eliminated bugs that we've already fixed. (It's not useful for us to dig into bugs on older versions of our software -- in other words, why look for a solution to a problem that might've already been fixed?)

>> "- connected to the internet"

If TA can connect to the internet and reverify with the servers then it will convert the offline activation to an online activation. This is by design.

Customers that wish to offline activate and never re-verify with the servers must implement a usable internet policy in their organization. (Meaning, actually block traffic).

If you're just testing things on your dev-machine then you need to re-create what happens in a real-life scenario for customers without internet access (namely, you need to actually prevent internet access).

But, like I said above, the first step is to upgrade TA to the latest version.

If TA can connect to the internet and reverify with the servers then it will convert the offline activation to an online activation. This is by design.> and is there anyway for us to see if this happened?> this might be the case as I was clicking around with internet connection after the offline activation

Customers that wish to offline activate and never re-verify with the servers must implement a usable internet policy in their organization. (Meaning, actually block traffic).> how & what to block? domains/ip's?> we've customers that go offshore for long terms, so while they are near the shore and have internet we would like to have them automatically updating their license, but if they are at sea for a long period (can be years) we don't want to block their usage of the program

to upgrade from 4.0.9.4 to 4.0.9.6 can I safely replace the dll (no interface changes / recompilation needed?)

>> "to upgrade from 4.0.9.4 to 4.0.9.6 can I safely replace the dll (no interface changes / recompilation needed?)"

Yes, but it's recommended to include the latest integration files (TurboActivate.h, TurboActivate.cs, TurboActivate.vb, etc. depending on your language) in your app and then recompile. Not doing that exposes you to bugs we've already fixed (thus wasting your time).

Reply
Discard post