There are many reasons why your license key may fail to work. These pages guide you through some common problems and how to fix them.
Note: The Foundry Licensing Tools’ default settings do not support RLM licensing on virtual machines (VMs). If you have any questions regarding licensing on VMs, please visit support.foundry.com for assistance.
Node-Locked and Client Licenses
If you have a node-locked license inside a client license file that is pointing to the server for its licenses, the node-locked license won’t work. You must use separate files for the node-locked licenses and client licenses. We recommend the following naming conventions:
• Node-locked - foundry.lic
• Client - foundry_client.lic
For example, the Mari interactive license in this client license file won't work because it is looking on the license server “red” for a license.
HOST red 000EA641D7A1 4101
LICENSE foundry mari_i 2017.1006 permanent uncounted hostid=000ea641d7a1 share=h start=6-oct-2016 issued=6-oct-2016 _ck=fbf430af8c sig="60PG4515BFTJCYAXSYJ6GTUJ3B9NRRGF3VUUKD022M0BXU48SSESUGSAFJ8BAD5BN883526ETKQ0"
You have set up a floating license, but client machines are not able to get a license from the server. Everything seems to be set up correctly. The server is running and is floating licenses. The client is correctly pointing to the server using a foundry_client.lic file or an environment variable. So what’s wrong?
This could be any number of things, but if everything is set up correctly, it could be the firewall on the server blocking perfectly legitimate requests from the client. In order to fix this, you need to specify ports for your servers and allow these to be open.
• If you’re on Windows, see Windows Firewalls.
• If you’re on Mac OS X, see Mac Firewalls.
• If you’re on Linux, consult your system administrator.
Accessing the RLM Web Server on Mac
On Mac, you’re browsing to http://<server_name>:4102, on the License Server itself, looking for the RLM Web Server page, but you can’t connect.
Due to Mac system architecture, you must add .local to the URL address when you’re browsing from the License Server itself:
Note: You can use this address on other platforms, but it’s not necessary.