MattLaunched an upgrade to an existing product with the new 4.0.9.3 ta binaries and a new .dat file.I have now two users who are shown as 0 days trial remaining, yet not showing as activated within the app.Trying to get more info as we speak, but the only way I can see this happening if is the IsGenuine has returned something other than Genuine, GenuineFeaturesChanged or InternetError. Is there anything else I should be looking for here?Users were trying to activate using TA.exe, and just getting "activation successful". Activating from within my app would give an exception as already activated.
What would be really useful in the TA.exe would be that it doesn't always default to using a stored key - e.g. give users the option to deactivate in there, or extend a trial even if they already have a key active on the computer.
I have managed to get one user working by sending a small deactivate executable. After running that, he was able to activate again (same key) with no problems.
Any ideas what is going on here? I can see that only 60 or so users have updated so far, and I have 2 x problems. This could be a looming support nightmare because I have no idea what is going on..
MattAdditional info:
1 user was able to activate again successfully after running a small deactivate tool that I sent him.
The second user gets the output NotGenuine when running the diagnostic tool I sent, but gets an "Activation Successful" when activating using TA.exe. So there is a discrepency here between what we are seeing from the dll and from ta. Any ideas what might be happening?
MattMore info:
User is running W10 64 bit.
I have sent him a small diagnostic tool, to which I get the following result:
IsGenuine(30,14,true): NotGenuineIsGenuine(): NotGenuineIsActivated(): FalseGetPKey(): Correct license key returned
Running TA.exe - no user input requested, "Activation successful".
I have a somewhat tame user here and its earlyish in my release. What more can I put into this diagnostic tool to resolve this issue?
Ideally, I will end up with a series of ta commands that I can run during license check that will fix this issue silently for my other users.
Are you mixing & matching versions of TurboActivate still? Don't do that. It can get confusing and hard to manage. Always use the latest version, and uninstall old versions of your app.
More information is needed -- namely, a way to reproduce this. Also, version number for every component used (TurboActivate.exe, TurboActivate.dll, the TurboActivate.dll your app uses, etc.).
MattWyatt wrote:> Are you mixing & matching versions of TurboActivate still? Don't do> that. It can get confusing and hard to manage. Always use the latest> version, and uninstall old versions of your app.> > More information is needed -- namely, a way to reproduce this. Also,> version number for every component used (TurboActivate.exe,> TurboActivate.dll, the TurboActivate.dll your app uses, etc.).
No mixing and matching here - just a straight upgrade to 4.0.9.3 (from a much earlier version).The issue seems to be that IsGenuine is always returning NotGenuine, IsActivated returns false yet TA.exe is saying all is well. On most of these computers, the existing activation would have been made with an older version, but in our testing moving up to a new version across the board hasn't been as issue. But now that we have released, 2/ ~50 have had issues.
If you can let me know what to put in a small app for this user to run (beyond what I have already tried), and also perhaps a way in code that might resolve it that I can run as part of my app, that would be great.
MattWe're getting more reports of issues now.
The jump is from version 3.4.7 to 4.0.9.3, no other change just users getting a NotGenuine but unable to resolve by activating with TA.exe. Please let me know what to do asap.
It almost sounds like you're running into the problem of not checking if the user is activated when IsGenuineEx() fails (i.e. not checking if the is is not activated because X days has elapsed or because they never activated in the first place): https://wyday.com/limelm/help/using-turboactivate-with-csharp/#check-activation
Because the TurboActivate Wizard just calls IsActivated(). It never calls IsGenuine() or IsGenuineEx().
