NI Volume License Manager Logs DPLT Diagnostic Functionality Message

Updated Sep 8, 2026

Reported In

Software

  • Volume License Manager

Issue Details

After starting NI Volume License Manager (VLM) or importing a new license file, I see the following messages in the lmgrd.log file:
 
Diagnostic Functionality is Unable to Access AF_UNIX Socket

DPLT: Diagnostic Functionality is not supported on this platform
 
I am concerned that these messages indicate a license server failure or prevent it from hosting or allowing client machines to check out licenses.

Solution

If you see these messages in lmgrd.log, they are typically informational and do not, by themselves, indicate a failure of the NI Volume License Manager server.

 

During startup, the FlexNet licensing components used by NI Volume License Manager attempt to initialize diagnostic functionality. This diagnostic functionality attempts to use AF_UNIX sockets during initialization.

 

On some Windows operating systems, AF_UNIX socket support may be unavailable or unsupported. When the licensing engine cannot access an AF_UNIX socket, diagnostic functionality cannot be initialized, and it logs the messages above.

In most cases, these messages only indicate that diagnostic functionality could not be initialized. They do not prevent NI Volume License Manager from running, hosting licenses, or allowing client machines to check out licenses.

 

To verify that NI Volume License Manager is running normally:

  1. Open NI Volume License Manager on the server machine.
  2. Navigate to the Status tab and verify that Server State displays Running.
  3. Confirm that client machines can successfully connect to the server and check out licenses.

Additionally, check the compatibility between NI VLM version and server's operating system version.

If the server status is Running, clients can retrieve licenses, and there are no compatibility issues, no action is required and these log entries can be safely ignored.

Additional Information

AF_UNIX sockets were introduced in certain versions of Windows and may not be available on some Windows operating systems. When AF_UNIX socket support is unavailable, FlexNet diagnostic functionality cannot be initialized and reports the above messages in the lmgrd.log file.
 
Although the AF_UNIX-related messages described above are generally informational, additional troubleshooting is required if they appear together with vendor daemon termination or license server startup failure messages.
 
License server failures are typically accompanied by vendor daemon exit messages such as:
 
nilm exited with status 58
 
nilm exited with status 82
 
followed by messages such as:
 
Please correct problem and restart daemons
 
These messages indicate that the vendor daemon stopped unexpectedly and require additional troubleshooting to determine the underlying cause.