TurboActivate.exe crashedSolved

If I pass any argument into the TurboActivate.exe file from 4.4.2 Windows archive it fails with the strange crash report available in the Windows event viewer:

Faulting application name: TurboActivate.exe, version: 4.4.2.0, time stamp: 0x5ff4dfbe
Faulting module name: TurboActivate.exe, version: 4.4.2.0, time stamp: 0x5ff4dfbe
Exception code: 0xc0000005
Fault offset: 0x00009f3a
Faulting process id: 0x4860
Faulting application start time: 0x01d6ef6667478b15
Faulting application path: C:\Projects\PairTradeFinder\Source\PairTradeFinder\PairTradeFinder\bin\Debug\TurboActivate.exe
Faulting module path: C:\Projects\PairTradeFinder\Source\PairTradeFinder\PairTradeFinder\bin\Debug\TurboActivate.exe
Report Id: 371aaeb0-12a4-423b-ac45-6ad777b19fdf
Faulting package full name: 
Faulting package-relative application ID:

Out software uses TurboActivate.exe command-line arguments for passing additional activation data and running process after activation completion so it's critical for us to have this function working properly.

Did you forget to upgrade the TurboActivate.dll? That's what it looks like.

No. I've double-checked that. And moreover, it works fine if I just run it without providing command-line arguments. And it can be easily reproduced with TA binaries available for download from the https://wyday.com/limelm/api/ page and any valid .dat file - wizard starts fine if I just run it without any arguments but fails if I provide any argument into the command line.

We can't reproduce this. Can you tell us the exact commandline params you're using to reproduce a crash?

For instance, this command line fails (just nothing happened from the user perspective except the new error message in the Windows Event Log):

TurboActivate.exe --extradata="XXX"

Answer

We were able to reproduce and fix. Thanks!

4.4.2.1 is now out with the fixed Wizard (TurboActivate.exe) builds.

Reply
Discard post