richp01This weekend we had a massive increase in people contacting support stating their license key did not activate. We have not changed anything to our software or licensing. We would get the occasional failure to license the software. I need to be clear it is not really a failure. Our licensing currently has a two part communication. And it appears that we are timing out waiting for the final response from the server. The application is fine, but the customer needs to close the failure message and restart the application and it is fine.
Does anyone know if there was any change with the LimeLM licensing server?
Our licensing currently has a two part communication.
What does that mean?
The application is fine, but the customer needs to close the failure message and restart the application and it is fine.
It sounds like something is going wrong in your program. Give me a snippet of your code that failed and I'll help you out.
Does anyone know if there was any change with the LimeLM licensing server?
No, they're up and running and there was no downtime this weekend.
richp01What I mean by that is we ask the server if the is valid. After the response if the key is valid we then populate several User fields on the server.
Nothing has changed in the program and it was working fine as of Friday.
Thanks for the quick response. I just wanted to know if there had been any changes to the servers this weekend. May just be an anomaly.
No, we haven't had downtime scheduled or unscheduled in a while. We had about 5 minutes of scheduled downtime around January 1, 2014 to do some critical patches and security upgrades. But other than that it has been clean sailing this year.
If you give me more information about your error then I'll actually be able to help you (a full copy & paste of the error would be useful).
richp01Thanks Wyatt,
If there has been no changes to the License server then the issue is elsewhere. Thanks for your quick response.
richp01Wyatt,
Something was brought to my attention. Everytime our application runs it checks against the server to vaidate the license. So if we have revoked the key the application would stop functioning. Could this be the source of the issue where we are seeing an increase of activation issues. Not sure if maybe we are being throttled or limited because of this behavior.
Regards,
Rich
Could this be the source of the issue where we are seeing an increase of activation issues.
Perhaps, I don't know. I need more information. What was the exact error? And from which function?
Everytime our application runs it checks against the server to vaidate the license.
You shouldn't do that. If you *must* check often, then at most do it once a day. You can do that using IsGenuineEx() with "daysBetweenChecks" set to 1. We'd recommend something even longer than that (like 30 days), but even checking once a day is better than check once every time an instance starts up.
Not sure if maybe we are being throttled or limited because of this behavior.
We don't currently throttle or limit like that, nor do we have any plans to. If we ever did we would notify users, we wouldn't leave them guessing.
