We found out, that trying to check-out an expired trusted-storage based feature takes a lot of time (500-1000ms). Since our application uses several features to enable/disable parts of the functionality of the program this adds up to several seconds. Is there a way to work around this behavior?
As a test, are there any other license files or directories on the existing license path? (The lmpath utility will display the search path, as will the default lc_checkout error message; and setting LM_A_LICENSE_DEFAULT at run time can add to the path.) It might be that the libraries are searching multiple locations after the trusted storage checkout fails...
We don't use LM_A_LICENSE_DEFAULT for trusted storage. This is the output of lmpath.exe:
> lmpath.exe -status lmpath - Copyright (c) 1989-2007 Macrovision Europe Ltd. and/or Macrovision Corp oration. All Rights Reserved. Known Vendors: _____________
thermoco: C:\flexlm\license.dat _____________
Other Vendors: ______________
C:\flexlm\license.dat
We also noticed a lot of disk activity during the license checks that supports your assumption of having a lot of license directories to be checked, but lmpath only shows one..
