TA_IsGenuineEx & custom license fields

Hi,

I did the following:- created a license with custom field set to 4- activated a license on local pc- local field value is 4 (correct)- changed the custom filed value to 5 on the server- next day (after 24 hours) i called TA_IsGenuineEx with nDaysBetweenChecks =1 it returns TA_OK (instead of TA_E_FEATURES_CHANGED)- local field value remains 4 (not correct)- called TA_IsGenuineEx again, it returns TA_E_INET_DELAYED now- if I call TA_IsGenuine the local field value gets updated

Can someone explain what is going on, the field should get updated locally right?Is there a way to see that my client successfully contacted the server?(like 'last verification time' or something?)

>> "Can someone explain what is going on, the field should get updated locally right?"

Yes, presuming 24 hours has really elapsed. Faking it (changing time, date, etc.) will likely trigger the fraud detection algorithm and get inconsistent results.

>> "Is there a way to see that my client successfully contacted the server?"

Yes, TA_OK means it successfully verified either locally or on the server. For more information about the best way to get updated custom license fields to end-users, see our extensive documentation on the subject: https://wyday.com/limelm/help/license-features/#change

- For the record: I waited, so no cheating with time- TA_IsGenuineEx returns TA_OK, yet the fields are not updated locally- in visual studio i get notified that an exception of type long gets thrown (and its caught inside the lib); does that mean anything?so the issue is that for TA_IsGenuineEx (at least in version 4.0.9.4) this is not working as described on the page you linked to.

I've a mad client because of this, telling him to wait a few days before the fields get updated is acceptable, telling him to click a button isn't, so unless this is solved we will be forced to call TA_IsGenuine at startup. Since we have to release within a week is there anything I can to to speed up testing?

Can we see somewhere in the web interface that the client actually contacted the server or do I have to trace the network traffic for that?

Further details:the long that is being thrown during the TA_IsGenuineEx call is stored at memory address 0x0019ED98the memory there has the following value: 04 00 00 00 (followed by: 03 07 e1 07 <unititialized>) so the long that is thrown equals 0x04, does that make any sense to you?

Short answer: there's a bug in the logic in TA 4.0.9.6 that will be fixed in the upcoming 4.1.0.0 (we can shoot you the latest RC build in the meantime).

Description of the bug that has been fixed:

If the customer is still in the grace period, and TA_IsGenuinEx() fails to contact the servers then TA_OK is returned instead of TA_E_INET. In TA 4.1 (out soon) this is fixed and TA_E_INET is returned.

That's why you were seeing TA_E_INET_DELAYED the next time you made the call.

Long story short: your app was failing to contact the servers and thus the changed custom license fields couldn't be downloaded.

Shoot us an email at support@wyday.com and tell us the builds you need and we'll send you the pre-release versions (because we're still at least 2 months out from the official 4.1 release).

Send an email about the versions I need,What I still don't understand is why it failed to contact the server, whereas TA_IsGenuine doesn't have the same issue?

Reply
Discard post