Error -17 indicates that the client machine is having issues communicating with the license server.
Antivirus
If you're running an antivirus application on the server, then you may need to make an exception for the RLM application to allow it to communicate with the network
Windows server users can go to Firewall and Network Protection in the Windows Security App and select the option to "Allow an app through firewall". Following this browse to the installation folder and select the RLM app, then repeat for the Network License Manager app.
Check Ports
You will need to check that each of the ports used by the license manager are available to the network. There are 3 ports used by the license server for communication across the network:
Port
| Purpose
| Access | Comment
|
5054
| Web portal interface - http://localhost:5054/
| Optional
| Only required if you want to be able to access the web portal remotely
|
5053
| RLM License server
| Required
|
|
<VARIES>
| ISV Server port | Required
| By default this port is dynamically assigned on startup.
|
Note. You may find you need to open port access on both your server and client machines.
Finding your ISV Port
You can find your ISV server port from the web interface (http://localhost:5054) by selecting Status, then looking at for the port listed on the ISV servers table.
Testing port communications
In Windows you can test communications to your ports via a Windows PowerShell terminal using the following command
- Test-NetConnection -computername <SERVERNAME> -port 5053
Making a ISV Port Static
If you find that you need to open the ISV port in your firewall, then it is recommended that you change this to a static port. Details on how to do this are given in the following Bricsys Help article.