trial days left shows 0

Make sure the trial days is correct in your LimeLM dashboard. If not, edit it and save the changes, Then redownloa the TurboActivate.dat files and include them with your app (overwrite the old *.dat files).

Hello,

Thanks for the response.My trial version shows 7 days trial in limelm dashboard which is correct.But when i call trial days left function from my application it returns me 0 days left.

Any idea on this?

ThanksDhwani

Presuming you've followed the instructions in my previous post (re-download the TurboActivate.dat and overwrite the old TurboActivate.dat in your app). If after doing, and after making sure you're using the functions correctly (you must call UseTrial before you ever make a call to TrialDaysRemaining) then the answer is one of 2 things:

1. You've already used the trial on that machine. And thus the time has expired. Use trial extensions to add more days.
2. Or you're playing with the system date / time, TurboActivate noticed fraudulent behavior on the "user's" part (you, playing with the time) and thus said "No more trial days for you, Mr. Time Traveler".

So, don't play with your date time. And make sure you're using the latest TurboActivate.dat, TurboActivate.dll, TurboActivate.exe. And make sure you haven't already used the trial on that machine.

Hihaving similar issue - I was testing the trial part of the protection system, but suddenly, for the 1st time it gave me the result of 0 my code was pretty simple

TurboActivate.UseTrial();

int daysLeft = TurboActivate.TrialDaysRemaining(); //-> gives me 0

I've followed the previous instructions - redownloaded the turboactivate.dat and replaced italso I did not do any time changes so far.....

The only thing I could guess is that I've started testing from the registration code, not from trial...I did full cycle with registration code, all went fine, then I've deactivated it from the dashboardand now I"m having this kind of issue.

Please let me know if this is expected behavior.

I'm assuming you set the trial days to non-zero in your LimeLM dashboard for that version.

Deactivating a license doesn't reset the trial. In fact the 2 systems are completely separate. So if you started a trial, your trial length is 14 day, then you activate your app and use it for 14 days, then deactivate the number of trial days remaining is 0.

Also, if that's not what you did, were you playing with the date/time/timezone? If so, TurboActivate detects that and says "I can't trust the system time because the user has been screwing around with it, so I'm just going to set the remaining trial days to 0".

Hithanks for the answeractually number of trial day in my case is 1 (one). and that was set just from the very start.the question was - is it possible to test trial right after correct registration key was entered (and later on deactivated)Of course this is not a work scenario (it'll probably never happen in production), but the issue is that I can't test trial 🙂

I did not use the TurboActivate.UseTrial();code when I was testing normal regcode.I've started to use it (trial code) just yesterday. and the very 1st answer from TrialDaysRemaining() was 0!

Also I did not change date/time/TZ, for sure.

as far as I understand, trial system could be used just once on one PC, so I'm going to test trial on another PC today.This time I'll begin testing from tial subsystem.

By the way, could it be that once I've started trial, the specified value (one) was decremented and that's why I've got zero as response? at what moment you are decrementing the number of trial days?

2) Yet another question - does turboactivate support hours in trial, eg 12 hrs?

I did not use the TurboActivate.UseTrial();code when I was testing normal regcode.

The TurboActivate wizard does, though. So if you were playing around with that, then that's what called UseTrial().

as far as I understand, trial system could be used just once on one PC

You could always extend the trial.

2) Yet another question - does turboactivate support hours in trial, eg 12 hrs?

No. Trials can only be in days.

Sam wrote:> The TurboActivate wizard does, though. So if you were playing around with that, then> that's what called UseTrial().

I've not used Wizard at all, only using java code

still would like to hear the answer on questions1) how remaining days being calculated (taking into account that I've specified just 1 day)2) my test scenario - 1st regcode then trial, would like to hear your comments

thanks

1) how remaining days being calculated (taking into account that I've specified just 1 day)

I'm not sure what you want explained. You set the trial to 1 day. After 1 day (a.k.a. 24 hours) has passed then the trial is over.

2) my test scenario - 1st regcode then trial, would like to hear your comments

If the user deactivates and there's still time left on the trial then they'll be able to continue to use the trial.

>I'm not sure what you want explained. You set the trial to 1 day. After 1 day (a.k.a. 24 hours) has passed then the >trial is over.

pardon me, probably I'm not very clear with the issue description.lets try this way:

1) I've integrated TurboActivate into my project (java)2) I've started to test things (without any trial code!) as a regular way, ie using registration code only - no questions here so far.3) I've deactivated reg code on site (the state become NotGenuine, that's OK)btw, I've used this code to do online activation each run - IsGenuineResult gr = TurboActivate.IsGenuine(0, 14, true, false);was that the right way?4) I've added trial code (shown above) and the very 1st run after adding shown me 0 days left (1 day was specified for trial time and 1 day did NOT passed at the moment of testing), ie I did everything in a couple of minutes.

hope its clear now.P.S. my only guess that such kind of testing is not supported and the correct way was to first test trial and only then reg code?

3) I've deactivated reg code on site (the state become NotGenuine, that's OK)btw, I've used this code to do online activation each run - IsGenuineResult gr = TurboActivate.IsGenuine(0, 14, true, false);was that the right way?

You shouldn't use 0 for the first parameter. It's overkill and is a bad experience for the user. We recommend 90 days.

4) I've added trial code (shown above) and the very 1st run after adding shown me 0 days left (1 day was specified for trial time and 1 day did NOT passed at the moment of testing), ie I did everything in a couple of minutes.

We can't reproduce this here. You said you were going to test it on another computer. Did you get the same result?

>>You shouldn't use 0 for the first parameter. It's overkill and is a bad experience for the user. We recommend 90 days.

agree, I've used 0 just for tests, to have the latest info from server each run, in production 90 will be used

>>You said you were going to test it on another computer. Did you get the same result?

tested today these scenarios:

1) live linux (Ubuntu 12.04 LTS x64) - all fine, got 1 day after trial was used2) MaxOS (inside virbual box VM) - all fine, got 1 day after trial was used3) Win xp SP3 Eng Prof x32 - same issue as on host - 0 days of trial right after Trial was used! (no one day passed)4) changed trial days to 2, then to 10 - same effect, 0 days left on host system (win7 x64)taking into account that I've just started to test TA trial subsystem, 10 days would really return me value >0!?

please assist.Thanks in advance(and yes, I've downloaded .dat file each time after exp days changed on site) and replaced it.

Go into TurboActivate.java and add breakpoints on the "switch(ret)" lines of both the TrialDaysRemaining() and UseTtrial(int flags) functions. Tell me what the "ret" values for both of those is.

test done, results:ret value for TrialDaysRemaining() is 0 (also it returns 0 as value for remaining days)ret value for UseTrial(int flags) is 0 (flags = 2)

I guess my work machine (win7x64 sp1 eng ult) has some issues that influence the TA trial system. I do understand that internal mechanics under the hood is a private info, so I wont insist on following investigation.yesterday I've tested a start of trial on another windows and it returned the correct expected value (10 in my case).

if you would like to debug my case - let me know how I could help.Thanks