Tuesday, October 2, 2018

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

If you get this message in LMTOOLS there is probably an easy solution. This is something I run into with the Autodesk Network License Manager version 11.14.1.3.

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

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

Trying to start the license service (the service name is shown in LMTOOLS > Config Services > Service Name) manually in Windows Services (run services.msc) can give this error:
”The Autodesk Licenses service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.”

image

The last row in the FlexNet debug log may be:

(lmgrd) SLOG: Summary LOG statistics is enabled.

Perform status enquiry could show something like this:

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:   SERVERNAMEHERE
License path:  @SERVERNAMEHERE;
FlexNet Licensing error:-15,570

Solution

Right click on the service and select Properties followed by the tab Log On and note that Local Service account may be used. Change that to the Local System account and then start the service.

Not sure why the wrong account is used when creating the service with LMTOOLS but it sounds like a bug.

image

If still not working there are some other solutions to try:

  • Check the Server Status. If you see FlexNet Licensing error:-1,359.  System Error: 2 "No such file or directory":
    • Make sure the license file path in the Config services tab is correct.
    • Make sure to click the option "LMTOOLS ignore license file path environment variables", and then try to restart the service.
    • Make sure your antivirus software is not modifying the Windows services, e.g. "Sophos Endpoint Security" has been reported to cause the -1,359 error.

If you now got it working and also would like to create license usage reports head over to JTB FlexReport.

Some of the latest blog posts

Subscribe to RSS headline updates from:
Powered by FeedBurner