Summary
License Manager Status / Vendor Daemon Status is "unknown" or "down"
Question
License server is running but License Manager Status / Vendor Daemon Status is unknown or down status.
Environment
- FlexNet Manager for Engineering Applications 15.x
- FlexNet Agent 5.x
Answer
There are some reasons of this problem.
- Agent is down
- Start FlexNet Agent and make sure it is "up" status on FlexNet Manager for Engineering Applications Web console.
- Agent cannot access the configured lmgrd
- Make sure "lmgrd Executable Location" is configured a correct lmgrd executable path.
- FlexNet Agent 5.3 or before does not work if "lmgrd Executable Location" value is a symbolic link path. Update the value to the physical path.
- Agent cannot access the configured lmutil
- Make sure "lmutil Executable Location" is configured a correct lmutil executable path.
- FlexNet Agent 5.3 or before does not work if "lmutil Executable Location" value is a symbolic link path. Update the value to the physical path.
- Agent cannot access the configured license file
- Make sure "License Files and Directories" is configured a correct license file path.
- FlexNet Agent 5.3 or before does not work if "License Files and Directories" value is a symbolic link path. Update the value to the physical path.
- The configured lmutil version is older than vendor daemon
- Compare the base FlexNet Publisher version of both lmutil and vendor daemon.
UNIX
% lmutil lmver <path>/lmutil
% lmutil lmver <path>/<vendor_daemon>
Windows
> lmutil.exe lmver <path>\lmutil.exe
> lmutil.exe lmver <path>\<vendor_daemon>
- The configured lmutil is corrupted
- Make sure lmstat returns a license server status.
lmutil lmstat -c <license_file>
- The vendor daemon path in the license file is invalid
- Make sure the configured vendor daemon path in the license file is valid.
- For FlexNet Agent 5.3.1 or later, it is mandatory to specify the daemon executable name in the path (IOJ-1728848).