This page is related to key-based licenses — a regular license type used in TestExecute 15.40. For information on the new ID-based license type, see SmartBear ID-based Licenses.
After you activate your TestExecute license, TestExecute’s licensing subsystem stores the license information to a secure location on your computer and checks it when you run TestExecute.
Below are typical situations when TestExecute fails to check the license information after rebooting.
-
The license may be lost after rebooting if the operating system is installed on the dynamic disk. To check whether the disk is dynamic:
-
Click Start | Control Panel.
-
In the Control Panel window, select the Administrative Tools | Computer Management | Storage | Disc Management category.
-
In the Disk Management window, check the Type of the disk on which the operating system is installed.
If the target disk has the Dynamic type, we recommend that you convert the disk so it has the Basic type. For this purpose you can use special tools, for instance, EaseUS Partition Master or similar tools.
If the license does not appear after converting the disk, please contact the SmartBear Sales Team for a new license key and assistance in resolving the problem.
-
-
Some protection products like Windows 7 Manager, CCleaner or Microsoft Malware Protection may prevent the licensing subsystem from accessing the license information or may remove this information from the machine. This typically happens after you reboot the computer. Since the licensing subsystem cannot find the license information, it reports to TestExecute that the license was not found and TestExecute is unable to start.
This problem can occur if you use malware protection products on the server where the license is activated.
If you lost the license and have malware protection software on your License Manager PC, please contact the SmartBear Sales Team for a new license key and assistance in resolving the problem. You will have to uninstall this protection software and activate the license with the new key.
For more information on the causes of why TestExecute may fail to find the license, see License Check Problems.