Troubleshooting License Manager Problems

The following is a guide to troubleshooting problems with licenses using the Intel® Software License Manager. 

  1. Are you using the latest version of the license manager?  You can download it from the Intel Registration Center in the Products list after signing in.  For more information, refer to "Intel® License Manager for FLEXlm* Servers." 
  2. Have you downloaded a 2016 version product as an upgrade to a 2015 or earlier version?  If so, your license has also been upgraded with a new serial number.  Sign into the Intel Registration Center to download your new license file, and replace the old file on the server with it.  Be sure to restart the license manager.  For more information, refer to "How do I get my license file for Intel® Parallel Studio XE 2016" and "How to Upgrade 2016 Floating License."
  3. Is your client using the correct license file?  Check your INTEL_LICENSE_FILE environment variable.  If it contains a file path, make sure the file contains the correct server name.  If it does not contain USE_SERVER, make sure the file is the same one the license manager is using.
  4. Is the license file valid?  The license may be invalid if it has any of the following:
    1. An incorrect host ID or server name.  To update this information, follow these steps: "How do I change the Server/Host data I provided for my floating license?"  Note that if there are three license host servers, all three must have a unique name and ID.
    2. An expiration date earlier than the product build date. 
  5. Do you have any old or invalid license files in the license folder?  Be sure the folder(s) pointed to by INTEL_LICENSE_FILE or /opt/intel/licenses on the client machine only contains current files.  Having old files will add to the checkout time, particularly if they contain invalid server information.  On the license server, make sure the flexlm license folder only has valid floating license files. 
  6. Is there a firewall preventing access to the TCP port for the license manager?  The default is 28518.
  7. Is there a firewall preventing access to the vendor daemon port?  This can be specified in the license file, or selected by the license manager.
  8. Is the license manager running?  On the server, run lmstat:
    1. For Linux execute lmstat -a -c <license file> where <license file> is the name and path to the floating license file. 
    2. For Windows execute lmutil lmstat -a -c <license file> where <license file> is the name and path to the floating license file.
  9. Do you get the error message "Package might be for the wrong platform or corrupted?"  Check that your Linux Standard Base (LSB) compliance version is 3 or later.  See this article for a description and solution: FLEXlm License Manager 2.0 may fail when LSB 3 is not met 

If you're still unable to use your floating license please file a support request at Online Service Center Be sure to select the product you need help with from the product list. You can also look for answers or submit a new thread in the related forum.

To better assist with your issue, please provide as much of the following as possible:


  1. The serial number for your floating license.
  2. The name of the specific Intel FLEXlm license manager server file you downloaded and installed.
  3. OS and architecture for your license host server system(s).
  4. OS and architecture for your client system(s).
  5. The license files for both the server and client.
  6. Values to which the INTEL_LICENSE_FILE (client) and LM_LICENSE_FILE (server) environment variables are set.
  7. Verification that the Intel License manager is running (capture of the results of running the appropriate lmstat command)
  8. A debug log.  On Linux* or OS X*, set INTEL_LMD_DEBUG to /tmp/licensecheckout.log and on Windows*, set INTEL_LMD_DEBUG to C:\temp\licensecheckout.log and run the client. Once the client finishes execution, attach the licensecheckout.log to the support issue.
  9. If you are opening a support request about a segmentation fault issue, attach the stack dump.
For more complete information about compiler optimizations, see our Optimization Notice.