License Check Problems

Applies to TestLeft 15.40, last modified on March 17, 2022

This page is related to key-based licenses — a regular license type. For information on the new ID-based license type, see SmartBear ID-based Licenses.

When starting, TestLeft connects to the Sentinel LDK License Manager service running on your computer or on your License Manager PC and requests permission to run. If the License Manager permits the run, TestLeft will start, otherwise, it will show an error message informing you about the problem.

Below are some typical causes of the license check problem:


  • TestLeft cannot start if the license has not been activated. For instructions on license activation, see Activating Licenses.

  • TestLeft cannot start if the Sentinel LDK License Manager service is not running.

    To determine whether this service is running, open the Control Panel | Administrative Tools | Services window and see whether the services list contains the Sentinel LDK License Manager service and that the service is running.

    If you have a Floating User license, check whether the service is running both on your computer and on your License Manager PC.

    If the service is not running, try to start it. If this does not help, reinstall TestLeft or the License Manager utility and try again.

Specific to Floating User Licenses

  • Your computer and the License Manager PC must have a functioning network connection. If one of these computers does not have network access, the license check will fail. To solve the problem:

    • Verify that your computer has a working connection. Make sure that the network cable is connected to your computer. Perform the same actions on the License Manager PC.

      If you are launching TestLeft on a virtual machine, check whether this machine has a network card and whether its host computer is connected to the network.

    • Check that your computer can access the License Manager PC. For instance, you can “ping” this PC. Perform the same actions with the License Manager PC.

  • By default, to find the License Manager PC, the licensing subsystem uses broadcast requests. This type of request may not work in certain types of networks. For example, it will not work if the License Manager PC is outside of the local network, in which your TestLeft workstation resides. Also, such requests may not function in Virtual Private Networks that are configured in a certain way.

    To solve the problem, on the TestLeft workstation, you need to specify the License Manager PC, to which the TestLeft instance will connect. See Specifying License Manager for Connection.

  • The Sentinel LDK License Manager service uses the TCP and UDP protocols and port 1947 to transfer data. Make sure that firewalls or proxies running on your computer and local network do not block these protocols and the port. Ask your network administrator for help with configuring the firewall or proxy settings if needed.

  • The license check fails if the number of currently running instances is equal to the maximum number allowed by the license. In this case, close the instances that are not needed or upgrade your license to a greater number of allowed instances. See All the Product Instances Allowed by Your License Key Are Already in Use (Running).

  • The license check may fail if the License Manager settings deny your user account to access the License Manager. For more information about the problem and a possible workaround, see Access to the License Manager is Denied.

You can also try resolving the problem by using the Licensing Troubleshooter on our web site:

Licensing Troubleshooter

See Also


Highlight search results