 |
Important Notice for ReadyAPI Customers |
ReadyAPI has fully transitioned to the ID-based SmartBear License Management (SLM) system. We are now moving into the final phase of deprecation of file-based licenses. Customers still using file-based licensing need to plan for migration to SLM before September 30, 2025.
If you are still in the process of migrating or have yet to start, contact your Account Manager or SmartBear representative today. Our teams are ready to assist with smooth transition strategies. For additional support, please log a request with our Customer Care Team, who are standing by to help.
For further information and timelines, please refer to this page.
Below is a list of error messages that you might encounter when activating or deactivating floating licenses.
Failed to check out a license: Confirm that the license has been installed and has been allocated to users on the Floating License Server
Common cause: The license server cannot allocate any free license to you. This can happen for a variety of reasons:
-
No floating license is installed on the server.
-
The license is not allocated to you.
Suggested solution:
-
Run Management Console and connect to your license server.
-
Select License Storage from the menu on the left and check if the required license is added to the license storage.
-
Allocate the license to the desired user or user group.
Click the image to enlarge it.
For example, to make the license available to everyone, use the following user configuration:
See also Configuring the License Server.
Acquiring License Lock. Number of copies limit reached
Common cause: The license server failed to allocate the license. Most likely, the number of concurrent users for the license has been reached.
Suggested solutions:
-
Ask another user running ReadyAPI to close the product, or wait until the license becomes available.
-
Your system administrator can also free the license from the server. To do this:
-
Run the Management Console utility of the license server.
-
Click Connect to view the connection details.
-
Select License Sessions in the menu on the left.
-
Select the user who is using the license and click
. Enter the reason for which the license is revoked. The current user will receive a revocation notice and the license will be available to other users.
Click the image to enlarge it.
-
Acquiring License Lock. Connection refused to host
Common cause: The license was issued for a different address or port.
Suggested solution:
-
Make sure your firewall does not block the connection to the license server at the ports your license is bound to.
-
Make sure the IP address of your license server matches the IP address to which the license is bound. If the license is bound to a specific TCP port, this port must be specified in the service configuration file. Otherwise, the license server will use port 1099.
Click the image to enlarge it.
Failed to install license: Connection with License server could not be established. Check inputted IP and Port, and also firewall settings
Common cause: ReadyAPI cannot connect to the license server at the specified IP address or port. This can happen for a variety of reasons:
| Reason | Suggested solution |
|---|---|
| The license server uses a different port | Verify that you specified the correct port in the License Manager. |
| Firewall blocks the required port | Make sure your firewall does not block the connection to the license server at the ports your license is bound to. The default ports are: 1099, 10991, 9999, 9998. |
| The license server is not running |
Make sure the license server is running:
|
| The license was issued for a different port | Make sure the port specified in the configuration file is correct.
|
The hostName property is not specified explicitly |
Make sure the hostName specified in the configuration file is correct.
|
Non-JRMP server at remote endpoint
Common cause: ReadyAPI cannot communicate with the license server to retrieve the license. Below are some possible reasons for this.
-
A different service is using the specified IP address and port.
-
The license server’s host name, port or IP address has changed.
Suggested solution:
-
Check what service is listening for requests on the port you use to retrieve the license. You can use the
netstatcommand to list all open ports and find the ports you use to connect to the license server. If necessary, free the port and use it for the license server. -
Check what process is listening on the ports that the ProtectionLS process should use (default ports: 1099, 10991, 9999, 9998). Use the netstat command-line tool. Stop the process and restart the ProtectionLS application to start listening on those ports.
The license server installation file is corrupted
Common cause: The installation file was changed due to network issues.
Suggested solution:
Try to download the installation file again. To make sure the downloaded file was not changed during transmission, you can use a checksum:
| Installation file | MD5 |
|---|---|
| Windows x32 | dbf71a55af7a5b89c9c17b9497b34a84 |
| Windows x64 | 00054f8de62dd3e960b745d2b090ca8d |
| Linux | 1a25e984ac61b5a06c6514175748f62a |
| MacOS | 76b62ab54f64cb9406cd9678d243f043 |
Unable to access license server from another domain
In order to connect to the license server from an external network, you need to specify the name of the license server computer in the hostName setting in the server.xml file of the server. To learn how to do it, see Advanced Server Settings.
Remote administration is not allowed
Common cause: The License Management Console cannot connect to the license server. This can happen for the following reasons:
| Reason | Suggested solution |
|---|---|
The hostName property is not specified explicitly |
Make sure the hostName specified in the configuration file is correct.
|
Contact support
If you cannot find the error message above, please contact SmartBear Support.
See Also
Floating License Activation
Check out Floating Licenses on Headless Machines
Possible Issues With Floating Licenses