When AQTime starts, its licensing system searches for the License Manager on the local computer and in the network (see How Licensing Subsystem Works):
Below are some typical reasons why AQTime may fail to find the License Manager:
-
AQTime cannot start if the license has not been activated on the License Manager PC. To learn how to activate a Floating User license, see Activating Floating User Licenses.
-
AQTime’s licensing subsystem uses the Sentinel LDK License Manager service. If this service is not running, the license check will fail.
Make sure this service is running both on your computer and on the License Manager PC. The service is started automatically after the License Manager utility or AQTime installation. If this service is not running, activation is impossible.
To determine whether this service is running, open the Control Panel > Administrative Tools > Services window and see if the services list contains the Sentinel LDK License Manager service and that the service is running.
If the service is not running, try to start it. If this does not help, reinstall the License Manager utility (or AQTime) and try again.
-
Your computer and the License Manager PC must have a functioning network connection. If one of these computers do not have network access, the license check will fail. To solve the problem:
-
Verify that your computer has a working connection. Check that the network cable is connected to your computer. Perform the same actions on the License Manager PC.
If you are launching AQTime on a virtual machine, check if this machine has a network card and that 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 type of networks. For example, they will not work if the License Manager PC is outside of the local network, in which your AQTime workstation resides. Also, these requests may not function in Virtual Private Networks that are configured in a certain way.
To solve the problem, on the AQTime workstation you need to specify the License Manager PC, to which the AQTime instance will connect.
To solve the problem, modify the search settings:
-
On AQTime workstation, open the
http://localhost:1947
URL in your web browser. This will open the Sentinel Admin Control Center. -
Choose Configuration from the menu on the left. This will display the configuration pages.
-
Switch to the Access to Remote License Managers tabbed page.
-
In the Specify Search Parameters box enter the computer name or IP address of the License Manager computer.
If you are using a VPN, enter the IP address as you see it in your network. See also Using AQTime in Virtual Private Networks. If the License Manager PC is outside of the local network, in which AQTime workstation resides, then specify the static external IP address of the License Manager computer (see also Using AQTime in WAN). -
Click Submit to apply your changes. Then try to launch AQTime again.
-
-
The Sentinel LDK License Manager service uses the TCP and UDP protocols and port
1947
to transfer data. Check that the firewalls or proxies running on your computer and local network do not block these protocols and 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 Product Instances Allowed by Your License Key Are Already 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 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:
See Also
Troubleshooting
License Check Problems -- Floating User Licenses