What version are you using? If it's not 4.1.8.1, start there.
Exception thrown std::ios_base::failure at memory location 0x013AE1Solved
I'm getting exception when calling
ret = Native.TA_IsGenuineEx(handle, ref opts);
from C#.
Here is the exception information:
Exception thrown at 0x764CC762 in XXX.exe: Microsoft C++ exception: std::ios_base::failure at memory location 0x013AE120.
Any idea, what it could be? It's *not* first-chance exception.
Thanks, I was using 4.1.6, the new one fixed the problem.
Well I've tested only Debug version of my app and it was working fine with 4.1.8.0, but seems like the Release version doesn't. And I downloaded latest 4.1.8.1 from your web, but the dll version is still 4.1.8.0.
Any idea?
Edit: It seems the problem appears only when the app is deactivated. Once I activated the app, it seems working.
>> "Well I've tested only Debug version of my app and it was working fine with 4.1.8.0, but seems like the Release version doesn't."
What do you mean by "doesn't work fine"? Full error codes, reproducible code, etc., etc. are needed: https://wyday.com/limelm/help/faq/#useful-reports
>> "And I downloaded latest 4.1.8.1 from your web, but the dll version is still 4.1.8.0"
That's correct. 4.1.8.1 is a minor update to 4.1.8.0 (just API fixes, the libraries are identical)
Yes, sorry - the exception I get:
Exception thrown at 0x764CC762 in XXX.exe: Microsoft C++ exception: std::ios_base::failure at memory location 0x01BFE440.
And it's thrown when calling:ret = Native.TA_IsGenuineEx(handle, ref opts);
We can't reproduce this with the latest released version. Make sure the latest versions of TurboActivate.dll / .exe are in both your Debug and Release folders.
They are, I checked several times. I also changed the TurboActivate.dat file to latest one (it was different).
I add the dll and dat files inside exe as an resource and unpack them when app starts to different directory (temp) and delete after. But I've added them to installation directory as well and was not working. Both Debug and Release use the same dll.
We'll keep digging. Are you using the 32-bit or 64-bit version of TA?
We can't reproduce this. Please send an example that reproduces this problem using the current version of TA. Send it to support@wyday.com.
32 bit.
It's 32 bit. The problem is, we have it in "big" application, don't know, what to send you to check.
Well, the next step would be to send a reproducible example to us. It doesn't matter how big it is (although if it's more than a few megabytes you won't be able to send it by email).
My guess is that you forgot to replace one of the TurboActivate.dll files and it's still lingering there as an old version (which would explain why Debug works but Release doesn't).
It's working now, sorry for that - my mistake. There is some first-chance exception being thrown in TurboActivate.dll, but that's pretty ok (since it's handled). I thought it was the reason, why my app kept crashing (it was not).