Error Summary

Message:
FAILURE: Unable to reach a network server. Authorization failure.
Details:
There is no available license for @RISK.
Log reference: PalFlexServer8.log may show:
RequestFloatingLicense failed with error code 43: Ensure system date and time settings are correct.

This usually happens when the client cannot acquire a license from the server. The root cause could be on the client, server, or network.

Step 1: Determine where the problem is

• If all clients fail → problem likely on the server.

• If other clients work → problem likely on the client device or its network connection.

Step 2: Server Troubleshooting

1. Verify license activation

   • Open Server Manager → confirm the network license is active and current.

2. Check firewall settings

   • Allow Palisade.exe and lmgrd.exe to send/receive traffic.

3. Verify license process

   • In Server Manager, check Status → should show Palisade UP.

   • If not, click the magnifying glass → View to see logs.

   • Most common cause: port conflict.

4. Check for port conflicts

   • FLEXnet licenses from other vendors may conflict.

   • Ensure lmgrd ports are unique.

   • Avoid using vendor daemon ports in the range 27000–27009 if dynamic ports are used.

5. Server.lic file

   • Avoid manual editing; use Server Manager.

   • SERVER line format: computer_name ethernet_address lmgrd_port

     • this_host is allowed for computer name

     • ANY is allowed for Ethernet address if using activatable licenses

Step 3: Client Troubleshooting

1. Check system time

   • Make sure client time matches server time.

   • Windows: Settings → Time & Language → Date & Time → Sync now

2. Check server name and port

   • On client: License Manager → Select License → Concurrent Network

   • Server name must match Server Manager hostname.

   • Port numbers must match server configuration.

3. Software version compatibility

   • The server version so be the same or later than the client version.

4. Test LMGRD port connectivity

   • Using PowerShell:

     test-netconnection servername -port 8090
     

   • Using Telnet:

     telnet servername 8090
     

   • Blank screen = port open; error = blocked.

   • Note: the port 8090 is the default on the License tab. If this has been changed on the server then use the updated port number.

5. Vendor daemon port

   • Server Manager → magnifying glass → View → find Palisade using tcp-port

   • Test this port using PowerShell/Telnet as above.

6. Subnets & network names

   • Different subnets may require fully qualified domain names:
     portnumber@servername.company.com

   • Update registry keys if needed:

     HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Palisade\Licenses
     HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE
     

7. Client firewall

   • Allow PalFlexServer8.exe to send/receive.

8. FLEXnet timeout

   • Some networks with many hops may require longer timeout than default 0.1s.

Recommended Approach

1. Confirm all clients vs single client issue.

2. If server-side:

   • Check license status, firewall, and port conflicts.

3. If client-side:

   • Sync time, verify server name/port, check firewall, test connectivity.

4. If network:

   • Test ports using PowerShell/Telnet and ensure no intermediate firewall or router blocks.

Related Articles

Network Ports and Firewalls

Redirecting Concurrent Clients to a New Server or Port Number

Install Server Software

Network Ports and Firewalls

Edit the Server Name in the Client.ini file 

Network Ports and Firewalls.

 FLEXlm License Manager Times Out