Product is activated, but TA_IsGenuineEx() always returns error 0x3Answered

Just to follow up on this.  I also looked at the result of TA_IsActivated() in addition to TA_IsGenuineEx().  When it executes:

hr=TA_IsActivated(taHandle)

The debugger reports S_FALSE as the value of hr

taHandle's value is 43 unsigned int.

Why does it report S_FALSE when clearly the activation occurred and was recorded to the key's entry on limelm.com?

Thanks,

Arie

The debugger doesn't tell you the error messages. It gives general Windows error messages.

Here's what 0x03 means.

/*
MessageId: TA_E_ACTIVATE
Message code (in Hex): 0x3
Message code (in Decimal): 3
MessageText:
The product needs to be activated.
*/
#define TA_E_ACTIVATE ((HRESULT)0x00000003L)

See TurboActivate.h for all error messages. As described in the FAQ.

Virtual machines become deactivated. Also described in detail in our documentation (FAQ, help article, ad-nauseam on this forum, etc., etc.). Use TurboFloat on VMs.

I have read that header file many times.  The product is shown as activated on your servers, but the code is saying it's not activated.  I will try TFS.

Installing the build we have with TFS also does not work.  I have verifed that the Windows VM does hit the TFS server we have, it reports the following in the log:

2023-02-10, 16:38:43 <notification>: New connection from IP: ::ffff:XX.YYY.ZZ.QQQ

Where XX.YYY.ZZ.QQQ is the public facing IP of the VM.  However, no user information is shown in the TFS log.  For example, we normally see the following for a successful request for a lease:

2023-02-10, 00:00:21 <notification>: New lease assigned (pcuser, 1, IP=::ffff:XXX.YYY.ZZ.QQ, PID=0). Expires: 2023-02-10 00:30:21 (in UTC). Used / Total leases: 4 / 25

This assignment log does notl appear on the server even when I request a new license from the app running on Windows Server 2019.

I'm about to go and check what the code is coming back with.

After debugging the app code using TFS, it looks like TF_RequestLease(tfHandle) returns 0x000000007: The storage control blocks were destroyed.  I understand that the debugger messaging might be incorrect, so I went to look up 0x7 error in the TurboFloat.h file.  It reads:

/*

MessageId: TF_E_WRONG_TIME

Message code (in Hex): 0x7

Message code (in Decimal): 7

MessageText:

This computer's system time is more than 5 minutes (before/after)

different from the TurboFloat Server's system time. Make sure

the server's Date, Time, and Timezone are set correctly and make

sure this computer's Date, Time, and Timezone are set correctly.

Note: That TurboFloat and TurboFloat Server work even if the timezones

       of the computer/server are different. In other words, your

       TurboFloat Server could be hosted in France and have a "client"

       computer running in New York (a 6 hour time difference) and

       everything will work fine provided both server and "client"

       have their date, time, and timezones correctly configured.

*/

I believe I messed with the time and timezone setting on the VM a few days ago, but changed it back.  Is there anything I can do to remediate the issue related to the timezone on the windows VM?

Even after setting the date and time to default, and then restarting the VM (same IP) it doesn't work.

Just to be clear on the client machine, the “Set time automatically” is “On" and the “Set time zone automatically” is “On”.  The TFS server has been working fine, so I'm doubtful it's the timezone / actual time setting in the server.