Page History

...

For more information, see System clock check. 

"WARN - License checkout not successful for session ..." error

LM-X License Manager may not work as expected if you get an error similar to the following:

2016-11-16 11:28:44,435 WARN - License checkout not successful for session Session ID/ Name. Error: LM-X Error: (Internal: 98 Feature: Name of feature)
System clock has been set back from 1970-Jan-01 00:00:00
For further information go to http://www.x-formation.com  

Assuming that LM-X client is embedded into an application running on IIS web server and, therefore, uses IIS_IUSRS identity, you need to have read access permissions to the following folder:

C:\Windows\SysWOW64\config\systemprofile\AppData\Local\x-formation

To resolve this issue, set read access permissions for IIS_IUSRS.

Why is my system clock set to a distant date in the future?

...

LM-X License Manager uses time_t, because this is the only portable representation of time across operating systems. If a file from outside the span specified by time_t (for example 1750) is detected by Windows, the Windows API changes the time to the one that fits the range represented by the time_t, thereby resulting in LM-X informing the user that system clock check has been set back from a random date.

To fix this problem, try to locate and reset the system clock using the LmxResetSystemClock tool to correct the time in the affected files. (See System clock check for more details.)

Problem with verifying system clock

If there is a problem with using lmxresetsystemclock.exe to synchronize you your local system's clock with a remote time server, you may see the following error:

...