LMpiot123Additional information:
-Windows 10-AMD FX(tm)-770k Quad Core Processor (information by task manager)
Interestingly last time it happened on AMD CPU as well. Any chance it's relevant here?
TA_CheckAndSavePKey failing
LMpiot123Hi,
I am coming back with this problem. This time I managed to get full information from the customer so I am 100% sure what is failing and that the customer is providing correct key.
What is happening:1)I call TA_IsGenuineEx(taHandle, &license_settings)2)This fails (produces error code different than TA_OK, TA_E_FEATURES_CHANGED, TA_E_INET or TA_E_INET_DELAYED)3)I then call TA_IsActivated(taHandle), this fails as well (code different than TA_OK)4)Now TA_CheckAndSavePKey(taHandle, key, TA_SYSTEM) is called and produces error code [0x1] = "FAIL (probably a wrong key)"
Points 1-3 are verbatim from the example code in C API files downloaded from you. What I've tried:
1)Running it as admin2)Running it with both TA_SYSTEM and TA_USER flags3)Restarting the computer4)Making sure no 3rd party antivirus is running
What the customer says happened:1)The software worked for him since around August 20162)They moved the computer to another apartment in the same town (Las Vegas, NV) and it stopped working suddenly
I am using the newest 4.0.9.6 version of Turboactivate, I've verified the key is correct (I've sent a debug version which prints the very same key which customer inserts). I haven't tried it locally because last time you told me that the key was activated/deactivated many times and it's hard to say which activation is from me and which is from the customer. I want to avoid this problem now but I do have suspicion it's going to work without problems on my computer (same as last several times the problem happened).
Is there anything we can do about it? Can we somehow remove all TurboActivate information from the computer and try again? What can is happening here? The problem is coming back from time to time and it's very frustrating because the only information we get is TA_FAIL from TA_CheckAndSavePKey function and nothing else. We really need some way to fix that or provide information needed to fix that.
Thank you for your consideration
LMpiot123
TA_CheckAndSavePKey() should only fail with TA_FAIL when the customer entered garbage input (i.e. no a product key, an/or the product key in the wrong encoding or with garbage attached).
Can you paste the code you're using for the product key entry? (I know you say you're using what's in the C example, but it's useful all the same to see exactly what you're doing -- there can be subtle implementation bugs).
Can you arrange a time we can do a remote debug with this user? I can do either today or tomorrow. Preferably business hours in Eastern Time (U.S.). Shoot me an email at wyatt@wyday.com
LMpiot123Hello,
Thank you for your answer. Your mention about possible implementation problem caused me to try another thing: make the customer run TurboActivate.exe from the official distribution.
This gave a TA_E_COM error instead of TA_FAIL at TA_CheckAndSavePKey.I've dig into your example code and found that you are doing this:
https://pastebin.com/6k4sz20f(code edited to leave important parts and remove trial code).
Important part is in line 11 when you are doing conditional:if (TA_IsActivated(taHandle) == TA_OK)
and then call TA_CheckAndSavePKey (line 19)
The problem is that according to the docs TA_IsActivated as well as TA_IsGenuine may return TA_E_COM themselves. The example code still calls TA_CheckAndSavePKey though and it's likely failing with TA_FAIL if one of the previous calls failed with TA_E_COM. I admit I should have logged previous error messages as well and not only the last one (I implemented it in a way to show the information to the customer so it was important that they don't get 3 different messages and as it happened I was just printing the last one from TA_CheckAndSavePKey).
Let me comment on one more issue as well. The issue from this thread:https://wyday.com/forum/t/4186/wmi-problems-again/
When customers are getting TA_E_COM error the tip is to check if WMI service is running. The customer had in fact both Windows Manamgement Instrumentation as well as WMI Performance Adapter services running. What was happening though is that CPU/RAM info was not available (Control Panel -> System -> System didn't show them either). This is apparently a reasonably common problem as quick google search proves. We were able to solve that on the customer's computer following the thread from Microsoft forum:
which has over 30 replies with various suggestions. We are unable to pinpoint which one was necessary to make it work.
Summing things up:1)I was only logging the last error key I was getting from TA_CheckAndSavePKey. This was failing with TA_FAIL even when correct key was provided, likely reason was that previous calls to either TA_IsGenuineEx or TA_IsActivated failed with TA_E_COM specifically.
2)WMI service running is not the only reason TA_E_COM might be generated. Maybe it would be nice if TurboActivate could give a bit more descriptive information or at least if the error message was updated to include the suggestion to check if CPU/RAM information is available in Control Panel (we are going to show that to customers now)
Thank you for your help. I hope information in this post is going to be useful for you.