Solution
This issue may occur by different possible causes which are covered in the following article with their respective troubleshooting steps.
Incompatible License File Version
Always use the most recent license file to make sure you have access to the newest versions of the software. A license file can be outdated if you have upgraded your software and NI VLM or FlexNET Publisher are still using an older version of the license file.
In the case of NI VLM, the software administrator should:
- Ensure that the licenses displayed in the Licenses view in License Manager are up to date and match the software version. The license file currently used by NI VLM can be found in the following file path: C:\ProgramData\National Instruments\Volume License Manager\nivlm.lic.
For example, if LabVIEW is licensed up to 2017 SP1 but LabVIEW Application Builder is only licensed up to 2017, Application Builder will not work in LabVIEW 2017 SP1.
- If the license file is not up to date, send an email to services@ni.com to request an upgraded license file. Include the following information: administrator name, administrator email, company name, and Service ID.
- (Recommended) Create a backup of the current server.
- Install the upgraded license file in NI VLM.
- Click Apply Changes.
- Restart the license server.
In the case of FlexNET Publisher, the administrator should:
- Contact NI technical support with your current NI License File to check up on what version you have access to.
- If your current license file is not up to date, send an email to services@ni.com to request an upgraded license file. Include the following information: administrator name, administrator email, company name, and Service ID.
- Install the upgraded license file in your FlexNET Publisher server.
- Restart the license server.
If you are unsure about your eligibility to activate newer software versions, contact NI for clarification.
Incompatible NI VLM or FlexNET Publisher Version
An issue may occur if the NI License Manager is not compatible with either NI VLM or with FlexNET Publisher. To review compatibility, please check the
readme file for your corresponding NI License Manager version to check what version of either FlexNET or NI VLM is supported.
The software administrator should:
- Check what NI VLM or FlexNET Publisher and NI License Manager version the license server is running.
-
If the NI VLM version is incompatible, upgrade it to a newer VLM version. If your software administrator is running the FlexLM/FlexNet Publisher, they will need to upgrade the vendor to a newer FlexNET daemon version.
Note: All the latest versions of NI VLM and FlexNET Publisher are compatible with all previous versions of NI License Manager. Upgrading VLM will not affect clients with older versions of NI License Manager.
License Server is Down
The software administrator should:
- Check that the server computer is on and the license server is still running in NI VLM or FlexNET Publisher.
- If the server is hosted on NI VLM:
- If the license server is stopped, navigate to Tools»Start Volume License Server. If you experience issues, refer to Unable to Start License Server When Using NI VLM for more steps.
- If the server is hosted on FlexNET Publisher:
- Open LMTOOLS»Start/Stop/Reread and click on Start Server.
Firewall on Server Side Blocking Client-Server Communication
Ensure the firewall on the server is not blocking the specified ports (default is 27000 and 4637).
The software administrator should:
- (Optional) Temporarily disable the firewall for testing.
- Configure the firewall to allow incoming connections on the specified ports.
Incorrect Permissions
In the case the software administrator is using NI VLM:
In the case the software administrator is using FlexNET Publisher:
- The software administrator should ensure that the client has the correct permissions assigned on the corresponding options file. If not, please review how to construct the options file to add the permissions.
Client Not Connecting to Server
The client should:
Note: If your volume license server is running on a port other than 27000, ensure that the port number is included with the server name (server:<port number>).
- Remove the server information to force NI License Manager to look at local licenses. Then, add the server and port information again.
- Click on the options menu in the top left-hand corner of the NI License Manager window.
- Select Manage Volume License Servers.
- Remove/delete the server name or address of your volume license server and click OK.
- Click the Refresh button at the top of the screen, then close and re-start NI License Manager.
- In the Network Licenses tab, you should now see No volume license servers configured.
- Select Manage volume license servers and re-add your license server's name or address and click OK.
- NI License Manager should re-initialize and pull the licenses from the server.
Refer to
Unable to Communicate With License Server Error in NI VLM for additional steps.
Check Debug Log
If any of these steps failed and the server is being hosted on NI VLM, the software administrator should:
- Check the NI VLM debug log. The log will confirm if the client attempted to check out a license and whether the attempt was successful.
If the server is being hosted on FlexNET Publisher:
If the debug log shows the client failing to check out a license, confirm the following:
Concurrent Unmanaged Licenses
If you are using concurrent unmanaged Licenses, the activation status under Network Licenses remains default grey even If you have access to them. This is a purely cosmetic issue and should not prohibit your access to the software. For more information, refer to Unable to Activate Software Using Concurrent Unmanaged Network Licenses
Corrupted options file
In some rare cases, there may be a problem with the options file.
If you are a software administrator please try to copy across the nilm.opt file on the license server from C:\ProgramData\National Instruments\Volume License Manager to the location of your original license file (where it was originally imported from) then restart NI License Manager on the client.