...
If there is a significant discrepancy between the LM-X license server and license client, your lmx-server.log file will report an error message similar to the following:[2013-09-24 11:44:07] CHECKOUT by pcuratolo@pcuratolo: FRONTEND
[2013-09-24 11:44:33] FAIL: Client pcuratolo@pcuratolo system time differs more than 24 hours. Please correct it!
[2013-09-24 11:44:33] CHECKIN by pcuratolo@pcuratolo: FRONTEND
[2013-09-24 11:44:33] FAIL: Client pcuratolo@pcuratolo system time differs more than 24 hours. Please correct it!
[2013-09-24 11:44:33] FAIL: New client pcuratolo@pcuratolo not allowed to connect.
This check is performed by LM-X to protect against deliberate attempts to set the system clock time in order to tamper with their license expiration time. To resolve this problem, you must ensure that server and client machine clocks are not more than 24 hours apart.
LMX_Free hangs when used within a dll file
When you have a dll, you typically have initialization code like the following:BOOL APIENTRY DllMain( HANDLE hModule,
DWORD ul_reason_for_call,
LPVOID lpReserved)
{
switch (ul_reason_for_call)
{
case DLL_PROCESS_ATTACH:
case DLL_THREAD_ATTACH:
case DLL_THREAD_DETACH:
case DLL_PROCESS_DETACH:
break;
}
return TRUE;
}
Using this code to initialize and free LM-X handles can cause LMX_Free to hang when using the DETACH handlers, because the OS can close threads without passing the information to the LM-X library. You should instead initialize LM-X by explicitly calling code to initialize and free LM-X from the exported dll interface.