Why won't the Intel® Software License Manager start on Windows*?

Published: 09/15/2017  

Last Updated: 09/17/2018

By Jennifer Dimatteo

Problem:

When trying to start the Intel® Software License Manager using the ilmconfig.exe or lmtools.exe utilities, you may experience a hang or see the following error:

License manager log error

When starting or stopping the service in lmtools, you will see an error related to the VD (vendor daemon) status:

LMTOOLS VD start

LMTOOLS VD stop

You will also see a WinSock error in the server status:

LMTOOLS WinSock error

 

Solution:

Although the first error message implies that the problem is with the license file, this is not necessarily the case. The primary cause is in the way it configures the vendor daemon to run as the Local Service account instead of Local System. This causes problems when trying to create the log file, as it does not have appropriate permissions.

To fix this, follow these steps:

  1. Open the list of services under the administrative tools or computer management. 
  2. Right-click on the service named Intel(R) Software License Manager and select Properties
  3. Under the Log On tab change the selection from "This account:" to "Local System account"License manager Windows account
  4. Click Apply

You should now be able to start the license manager.

While this is the preferred way to fix the problem, you can also change the log file to a path writeable by the Local Service account:

Lmtools configuration

For versions prior to 2.6, the path to the debug log file must contain a file name with the extension .log.  Version 2.6 may use .txt.

After making changes, click the "Save Service" button. You should now be able to start the license manager.

Have questions?

Check out the Licensing FAQ
Please visit our Get Help page for support options.

 

Product and Performance Information

1

Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.