Need new TurboActivate.dat file upon upgrading to 4.0?

Hi Team!

So, I'm moving over my app to build on VS2015. Everything is building fine after getting the new libraries and header files. But, for some reason the TA_CheckAndSavePKey() function is always returning an error. Specifically, the value of my HRESULT is this according to the VS2015 debug output:

0x0000001b: The drive cannot find the sector requested

What does this mean? As far as I am aware, the paths and required files are where they should be, but am not sure if it's something related to the .dat file or what.

Any tips?

Thanks,Arie

So I re-downloaded a new TurboActivate.dat file, placed it where my code points to but I'm still seeing the same error on the response from the TA_CheckAndSavePKey() function.

I thought maybe there is something wrong with the serial code being passed, but I don't think it is. Here's the code I'm using:

hr = TA_CheckAndSavePKey(taHandle, serial.c_str(), TA_USER);

That gives the error. To doublecheck that it's not the "serial.c_str()" parameter, I hard coded a product key into the function call as in the Example.c file. So I replaced the above with the following:

hr = TA_CheckAndSavePKey(taHandle, _T("XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX"), TA_USER);

Obviously, the XXXX are not really the code, but a product key that I know works when using an older build of my app with TurboActivate 3.6

Anyways, can you shed some light on this? Or tips for troubleshooting / debugging?

Thanks,Arie

Hey Arie,

TurboActivate.h contains all error codes and what they mean (Visual Studio gives you "Windows Specific errors" for hresult types, hence "The drive cannot find the sector requested"). But if you open TurboActivate.h, search for "1b", you'll see the real error:

/* MessageId: TA_E_INVALID_HANDLE Message code (in Hex): 0x1B Message code (in Decimal): 27

MessageText:

The handle is not valid. To get a handle use TA_GetHandle().*/#define TA_E_INVALID_HANDLE ((HRESULT)0x0000001BL)

Ah, I forgot to do the cross reference with the hex value that visual studio reported. Thanks, Wyatt. I will check to see if I am using TA_GetHandle() properly.

Arie

Reply
Discard post