Activate() always returns TA_E_EXPIREDSolved

Note : I changed the "trial length" to 0, and put it back to 30 this week. Could it be the cause ?

No, that's not it.

My customer checked its system date, and everything is ok. It's the second customer this week, I got this problem. Never had this problem before.With the first customer, I asked him to restart its computer, and he could activate the product.

What platform (Mac, Windows, Linux)? Also, what version of TurboActivate are you using (or, what versio is installed on these customers computers)?

Sorry I forgot the technical info : Mac OSX, TurboActivate v.3.2.2

I'll look into this.

This will be fixed in TA 3.3, out shortly. I apologize for the problem. We've modified our algorithm to account for "quirky" behavior in the Mac OS X kernel.

Ok : when the 3.3 version will be released ?

Shortly. We finished bug fixes for our customers running the beta. Now we just have to finish the updating the documentation.

Hello,

I ran into another issue recently : one of my customer was deactivated, probably after a call to IsGenuine().It seems to be the same problem as I describe earlier in this thread. It should be fixed by TA 3.3, right ?When do you think, you're gonna release it ? (Sam spoke about February, the 22th in a recent thread)

Thank you. Philippe

Yes, IsGenuine() is fixed in TA 3.3 as well. What happened for this customer is either they were blocking wyday.com (firewall, filtered internet, hosts file, etc.) or they were running into a "wifi login" page that was returned instead of the response from LimeLM.

Prior to TA 3.3, IsGenuine() would return TA_FAIL and deactivate the customer when running into any of those things. In TA 3.3 IsGenuine() will correctly return TA_E_INET.

When do you think, you're gonna release it ? (Sam spoke about February, the 22th in a recent thread)

Posthaste.

Strange ... To prevent this error, I do a ping to wyday.com prior to calling IsGenuine() but I guess my code is not perfect.Thank you. I'll wait for TA 3.3.

Hello,

Again, but I wanna be sure. Some customers (around 5%) reported me unexpected deactivations recently. The deactivation is occuring after a IsGenuine() call, just as written earlier in this thread.But I never had such problems before, so my question : did you change something on server-side ? Am I doing something wrong in my code ? Can I prevent this (I already sending a ping to wyday.com and executing IsGenuine() only if the request is ok) ?

My customers need proper explanations, so they don't panic : my product is used in realtime, so it's not acceptable to be deactivated in the middle of a show !

Thank you. Philippe

But I never had such problems before, so my question : did you change something on server-side ?

Yes, months ago. It's well tested and doesn't alter the previous behavior. Mainly just minor bug fixes and new features for TA 3.3.

Am I doing something wrong in my code ?

Perhaps, I'm not sure. I'd have to see your code.

Can I prevent this (I already sending a ping to wyday.com and executing IsGenuine() only if the request is ok) ?

Yes, with TA 3.3 will fix this problem.

Unfortunately pinging wyday.com doesn't cut it because this introduces a race condition between when you ping wyday.com and when you call IsGenuine(). Plus, if customer has an intermediate filter (wifi screen, hosts file intercept, DNS block, "web based" firewall block --- basically anything that "injects" itself into the response instead of the proper response from the LimeLM servers) then prior to TurboActivate 3.3 IsGenuine() would return TA_FAIL and deactivate the user. Plus if you're pinging wyday.com how do you know the response you're getting is actually from wyday.com and not a "filtered" response?

So don't ping wyday.com. It doesn't solve the problem (it actually introduces new problems).

My customers need proper explanations, so they don't panic : my product is used in realtime, so it's not acceptable to be deactivated in the middle of a show !

TA 3.3 is coming soon. If you want to push an update to your users right now using TA 3.2.2 then comment out your calls to IsGenuine(). Or wait another 24 hours for TA 3.3 and then include that and push that as an update.

Hello,

It has been 48 hours, and still no TA 3.3.No pressure, just info : so any news ?

Thank you. Philippe

We're uploading the files now. Once that's complete and we run a few sanity checks, we'll flip the switch and the latest version will be available for everyone. Just a few more hours.

Thank you. No pressure : stability and security first 😉

TurboActivate 3.3.3 is out. You can get it on your API page.