Different TurboActivate lib versions on the same product version

My users get error code 1 from TurboActivate, which is the general fail code. I have the following:

- A product (let's call it P) on LimeLM with one version V- Two separate software apps, both using the .dat data file for that product P version V. But the two apps are using different versions of TurboActivate.

When I run the app version using an older TurboActivate, I can register it. When I then run the app with the newer TurboActivate, it prompts me to activate, but fails with error code 1. I'm using different serials.

Is it a problem to use different TurboActivate versions on the same product version?

Yeah, if you're using the same activation data then you want to use (a) the same version of TurboActivate and (b) you always want to use the most current version of TurboActivate.

TurboActivate is backwards compatible with all old versions, but TurboActivate is almost never forwards compatible. That means you can always upgrade to the newest version of TurboActivate and the new versions will always be able to read the old data. But you can rarely use an old version of TurboActivate and expect it to read data written by a newer version.

That's just how we've designed it (it reduces our costs because we don't have to bend over backwards to make old versions read new data).

Short answer: always use the newest version of TurboActivate.

Thanks for the info!

Hm okay if it's backwards compatible, then this shouldn't be the reason for the errorbecause it's the *newer* TurboActivate which is showing the error code 1. If it was backwards-compatible, then it should just be activated after entering the serial in the older app version.

The app using the old TurboActivate is an old app version that has been shipped to customersso I can't make it use the newest TurboActivate 🙁

So, what causes error code 1? My customers report it, but I don't know how to solve it because it gives no information about the error reasons.

Are there any type of logging script that can be added to decipher in more detail what the Error Code 1 is?

No. We're continually adding new error codes to describe new error situations, but we don't currently have plans to add logging for internal behavior.

We need more information. Starting with a snippet of code that is failing. Are you trying to re-set the product key for a product that is already activated? If so, don't do that. A product cannot be activated with multiple keys on the same computer. Deactivate the first key and then activate a new key.

If you want to user multiple features for a single product key, then use custom license fields: http://wyday.com/limelm/help/license-features/

Short answer: we need a whole lot more information.

Reply
Discard post