Register license user rights Internet error

Hello all,

one of our clients, a large company, has problems with the registration on their laptops.They also tried outside their network (at home) with one of the laptops.

They basically get the "IsGenuineResult.InternetError". Are there any required user rights/Internet settings?

regards

Arie

Hey Arie,

On any well configured machine TurboActivate will work if no problem whatsoever. We also make significant efforts to make TurboActivate work on poorly configured machines as well (even going as far as to fix broken configurations).

Long story short, this FAQ article is the best place to start: http://wyday.com/limelm/help/faq/#internet-error

And make sure you're using the latest version of TurboActivate (currently 4.0.5.1). We've made significant improvements to our internet code to handle *tons* of misconfigurations, injections, etc.

Hello Wyatt,

tnx for your quick response.

I've contacted the client on the issue, they have an internet connection and can connect to wyday.com.

They can not switch off the virusscanner or the firewall on their laptops, they need admin rights for that (which is difficult at that company). But all those settings are default in their "Fenix" build which is rolled out standard on all laptops so are identical on all laptops. And since some of them do not have the problem ....

The rights on the filelocations and e.g. the windows registry may vary per user, can the problem be there?

Our problem is that we can, ofcourse, issue a new version with the latest update of the turboactivate, but they need about 2-4 weeks for the packaging and roll out, and they have a course on our software in 1-2 weeks 🙂.

greetings,

Arie

Also one other thing; At least on of the users had registered a couple of days ago, but lost its license the next day (same laptop) while it was registered (I checked it in the LimeLM dashboard). According their IT dept. the laptops are not rebuild on a daily basis.Now he can't register again due to the earlier mentioned issue. so weird 🙂

If you're using TA 3.x in the old build of your app, then the problem is likely the customer is disabling network adapters.

Temporary solution: don't do that. Don't disable network adapters.

Permanent solution: use TurboActivate 4.0 or newer. We've handled this interesting user-behavior by making TurboActivate smarter. So even if customers disable network adapters, TurboActivate will just work.