Your next step in troubleshooting is to ensure NI License Manager is configured to use a licensing server and can communicate with the licensing server. This is done in the NI License Manager user interface. Once NI License Manager is configured correctly and can communicate with the licensing server, you can confirm client permissions have been added to Volume License Manager.
An error might occur if the client computer is connected to a license server which is on a different domain than the client computer. To resolve this, add the server's domain to the client computer's DNS settings. To do this, complete the following steps on the client computer:
Note: If NI License Manager can’t contact the license server using the machine name, try <IP address>:<Port number>.
This means that NI License Manager was not able to communicate with the licensing server using the information provided in the Manage Volume License Servers dialog. This communication could be blocked by firewalls or possibly anti-virus software. If connectivity to the licensing server has not been tested already, see the Ping test and Telnet test troubleshooting guides.
If the client can successfully communicate via pings as outlined in the Ping Test, can communicate over the appropriate ports as is outlined in Telnet test, and is configured correctly in NI License Manager, it’s recommend to reach out to NI support for further troubleshooting.
If NI License Manager can connect to the licensing server, it should be able to request a license from the licensing server. Next, the licensing server needs to be configured to provide a license to the client in question.
Collaborate with other users in our discussion forums
A valid service agreement may be required, and support options vary by country.