kajWe use TurboActivate.I have a customer who is reporting an error code that results from calling IsGenuine and getting the response TA_E_INET.
I told him to check his internet connection and it appears fine - he can access wyday.com from his browser. What could be the problem here?
First, work through this: https://wyday.com/limelm/help/faq/#internet-error
If you're using the latest version in your app (and the customer is using that), and they / you have worked though that FAQ, and they're still having problems, much more information is needed:
kajFurther to this, the customer now has deactivated his key and is trying to activate a new key that I have successfully activated and deactivated elsewhere.
He is getting an error from TA_CheckAndSavePKey. I don't think that this function requires an internet connection. Is that correct?
I suspect that he has a corrupted executable or TurboActivate.dat file and I have advised a re-installation of the application.
>> "He is getting an error from TA_CheckAndSavePKey"
https://wyday.com/limelm/help/faq/#useful-reports
1. What's the error?2. What's the input?3. What's the version of TA?4. What's the OS you're running on?
Most of these problems can be solved by you without waiting for us by collecting the correct error codes, collecting the input, and reading the error code and descriptions in TurboActivate.h.
kajAfter telling him to turn off the firewall the user's IT department identified the problem, I received the email:
It was a firewall issue, not on the client but on our perimeter firewall. We enable SSL inspection to mitigate / manage security over the web. We believe the decryption of the SSL traffic is making the certificate dirty and invalidating the license check-in/ phone home procedure. Bypassing the check for the specific site wyday.com resolved the issue.
Is this a known issue?
>> "Is this a known issue?"
Well, yes. But this is not an issue. This is security 101. If an actor (malicious or not) intercepts or modifies traffic, TurboActivate will reject it.
This is expected behavior. Don't intercept / manipulate traffic to/from TurboActivate / TurboFloat or it will be correctly rejected as malicious or invalid.
