AR# 70200

2017.3 Licensing – lmgrd license server as a Windows service failed to start using LMTOOls.


I am able to start the license manager from the command line. However, I am having issues saving the configuration as a service using LMTools.

When I try to set up a Xilinx License Server configuration as a service using LMTools, I see the following message:

Windows preferred path <SystemDrive>\ProgramData to store service data is not set

I also see the following message, instead of "Started Successfully":

VD is starting, please check vendor daemon's status in debug log

The FlexLM Server Status shows the following:
Flexible License Manager status:
[Detecting lmgrd processes...]
License server status: <port_number>@<server_name>;
    License file(s) on <Server_Name>: C:\Xilinx\Xilinx.lic:
lmgrd is not running: Cannot connect to license server system.
 The license server manager (lmgrd) has not been started yet,
 the wrong port@host or license file is being used, or the
 port or hostname in the license file has been changed.
Server name:
License path:  <port_number>@<server_name>;
FlexNet Licensing error:-15,10.  System Error: 10061 "WinSock: Connection refused"

What is causing this issue?


In FlexNet Publisher 2015 (11.13.1), a change was made to run Windows license server services with LocalService privilege instead of LocalSystem privilege, following the least-privilege security best practice. 

One inappropriate consequence is that a lmgrd Windows service, as installed by installs.exe or lmtools.exe, might not start. 

This is because a LocalService service does not by default have sufficient privilege to write the server debug log to (a subdirectory of) Windows Program Files or Users directories. 

Flexera therefore recommends following Windows best-practice for writing application data by specifying the debug log and report log locations within a subfolder of %SystemDrive%\ProgramData\, as LocalService services do by default have sufficient privilege to write to ProgramData (sub)directories.

This information can be found in the fnp_11.14.0 released note (, page 10.

Therefore, to overcome this issue, please use the default location for the debug log file, for example, C:\ProgramData\FNP_DIR\ folder.

This is automatically pre-loaded for you when you are performing the configuration as a service using LMTools.

For example:


AR# 70200
Date 12/18/2017
Status Active
Type General Article