TurboActivate.exe successful with expired license

I have a situation where a license expired (months ago). It was previously activated online (online activation).

I need to do an off-line activation now. When I run TurboActivate.exe and point to .dat file it gives me License successfully activated (always). When I run the product, it prompts for a license code (as expected).

I'm using version 3.4.4, but prior license was issued with V3.3. Any ideas? Should I try to roll back TurboActivate.exe to version 3.3?

Note - we have online activation in our product and only use TurboActivate.exe when offline activation is needed.

Thank you

I need to do an off-line activation now. When I run TurboActivate.exe and point to .dat file it gives me License successfully activated (always). When I run the product, it prompts for a license code (as expected).

It sounds like you're using custom license fields to control when the license expires. The TurboActivate Wizard (TurboActivate.exe) doesn't look at license fields at all. It just looks at whether the customer has activated the machine or not.

So, if you want to have a customer re-activate when a custom license field value expires, then you should handle that inside your app. Does that make sense?

It does makes sense and I do use custom license fields.

Prior to reading your response, the customer did enable connectivity. Fortunately, I have a function to deactivate the license from within our product. Calling deactivate was successful (it previously failed with no connectivity). Also, I had previously deactivated their license on web, but calling deactivate within product also worked.

I then went into TurboActivate.exe to see if the wizard would start - and it did and started by prompting if I wanted to activate the license now. Previously it was just saying that the license was activated/genuine.

Calling deactivate successfully with connectivity seemed like it reset the license. I'm going to pursue the offline activation now.

Hi Wyatt - I need to reopen this issue from earlier this year concerning offline activation.

In the prior scenario, I have a disconnected system and the license has expired (based on my license parameter). I understand difference between activation and expiration. The product detects this correctly and prompts for a license activation, however the system still appears to be "activated" while the license has expired. I can't seem call deactivate() as it appears to require connectivity. It hangs and I handle the exception (and when I do have connectivity it works). When I try to start the TurboActivate.exe for offline activation, I just get that the license has been successfully activated. So I understand that the license is active, but my software checks the expiration date/policy and won't use it because it doesn't meet the license conditions. That was where we left of previously.

It seems like the TurboActivate.exe should have a way to force deactivation if the .dat file is provided in the command line argument list. In offline mode, I'm stuck... unless... should I be using deactivate(true)? Will this force a deactivation when offline?

Regardless, it seems like the TurboActivate.exe activation wizard should have a way do that (deactivate) regardless in an offline capacity.

Best regards and thanks,i10

To get new custom license field data you simply need to reactivate. See: Changing fields & getting the changed data in your app.

You don't need to deactivate first.

Thanks Wyatt - OK - I understand now. My app needs to accommodate this offline license change. I'll need to integrate the functions to generate the request file and load up the response file within my app if I use custom license fields like an expiration date or time-bound license parameter. That entails implementing the reactivation process for the very few cases where my customers require an offline activation.

Just want to reiterate... It seems like it would be a nice feature if the TurboActivate.exe had some type of reactivate functionality that, (only if the .dat file was passed as a command line argument) behind the scenes, would kill the existing license associated with that .dat instance and then would continue down the existing activation path to accommodate that license info update.

Thanks,i10 😉