masseyfHi,
I'm migrating to TA v4 and I'm encountering an issue with TurboActivate.exe. It seems that it won't recognize the --pdets parameter. Whatever I try I get the "The product detail file TurboActivate.dat could not load" error.
This simplest command line I use:
TurboActivate.exe --pdets="airimp40-turboactivate.dat"
This is the syntax still being mentioned in the help pages.
I tried with a path and without, with double-quotes and without, with other parameters and by itself, form a batch file and our application. Nothing works, always the same message. Of course all required files are present in the folder. We cannot use the .dat generic file name as our app can activate any number of products.
If I switch the TurboActivate.dll and TurboActivate.exe to v3.4.6 it works fine. Version 4.0.8.0 I'm trying just won't work.
What has changed? Was the documentation updated to reflect any changes?
By the way the download section says 4.0.8.2 but the file downloaded are 4.0.8.0.
Thanks.
Hey Francois,
You'll need to re-download the TurboActivate.dat file and everything will just work (we updated necessary fields in the TurboActivate.dat file, and older downloads of that files won't have it). Simply re-downloading and replacing will fix it.
>> "By the way the download section says 4.0.8.2 but the file downloaded are 4.0.8.0."
We'll look into that.
masseyfHi Wyatt,
Re-downloaded the dat file, renamed and still the same error.
If I rename the .dat file to turboactivate.dat and I start TurboActivate.exe directly there is no error. It will work with the "old" .dat or the new downloaded one. The .dat file is not the problem.
If I leave the turboactivate.dat file so named and start using the command line (with the --pdets parameter looking for the renamed .dat file), it still throws the error that turboactivate.dat is missing even though the .dat file is there.
If I remove the --pdets parameter from the command line it works (with the standard named .dat file present of course). Otherwise it throws the same error (as it should in that case).
The problem is really with the --pdets parameter. It seems to be looking for the file somewhere else than in the current directory even if a full path is specified.
masseyfCommand line with the standard name set in the --pdets parameter also throws the error (with the file present)!
turboactivate.exe --pdets="turboactivate.dat"
We'll take a look at that and see what the problem is.
We can reproduce this error, we'll have a fixed version out next week (probably Wednesday or Thursday).
In the meantime the only thing you can do is use the default "TurboActivate.dat" in the same folder as the TurboActivate.exe. We're sorry about that.
masseyfSuper, happy the issue can reproduced.
I basically have to put my conversion efforts on hold until this is fixed. As soon as you have something please let me know.
I can shoot you an unsigned debug build later today or tomorrow if that will work for you in the meantime. What builds should you need (x86, x64, or both)?
Hey Francois,
I've sent you an email with a link to pre-release 4.0.9 builds that you can use in the meantime (and fixes that bug).
masseyfHi Wyatt,
Received the link, downloaded and that new version fixes the problem. Thank you very much!
The version received is 4.0.8.3, not 4.0.9.
Sorry, yeah, it was 4.0.8.3. The "signed release" will be 4.0.9. We do separate version numbers for every "out in the world" release we make just so we can track down bugs, etc.
TA 4.0.9 is now out and fixes this bug. Thanks for reporting it.
