| Problem | Sentinel HL key drivers do not install. |
| Solution | Are older Sentinel HL key drivers installed on the machine? Uninstall the older driver using the installer corresponding to the older driver version. For additional information, see the Sentinel HL key driver documentation. After the older drivers are removed, install the Sentinel HL drivers. For additional information, see the Sentinel LDK Installation Guide. |
| Problem | The protected application cannot find a Sentinel HL key. |
| Solution | Does the Sentinel HL key LED light up? If not, this could be for one of the following reasons: >The key is not connected properly to the USB port. Disconnect, then reconnect after a few seconds. If the LED lights, the application should be able to access the key. >The required Sentinel HL key drivers are not installed. If you are running Sentinel LDK on a Windows platform, check for an entry for Sentinel LDK in the Device Manager utility. If there is no entry, you must install the drivers using one of the methods in the Sentinel LDK Installation Guide. >Check if the USB port is functioning correctly. Disconnect all other USB devices from their respective ports. Connect the Sentinel HL key to a different USB port. Try using a different USB device in the port from which the Sentinel HL key was not accessible. >Open the Windows Services window and check that Sentinel License Manager is running. >Check that the Batch Code on the Sentinel HL key matches the Batch Code of the protected application. |
| Problem | Web pages for Admin Control Center do not display in your Web browser on a Windows machine. |
| Solution | Check the following: >Confirm that the Sentinel LDK License Manager service is active. >Some other program that you installed may have incorrectly installed special TCP/IP drivers. As a result, WinSock configuration may be damaged. To resolve this problem, run the command |
E209 Sentinel Key Not Found How To
Press your windows key, type in services, and hit enter. Scroll down until you see any services beginning with the word Sentinel. Right-click and restart these services. Ensure you have the correct EdgeWise package installed ( standalone vs. Network EdgeWise) To confirm what package you need, unplug the EdgeWise Sentinel key. How to solve sentinel key not found (H0007).
Sentinel Ldk Protection System H0007
| Problem | The application takes a long time to find the Sentinel protection key on a large network. |
| Solution | It is recommended that you customize the search mechanism. Use Admin Control Center configuration to specify a search criteria, and to define the server addresses to be searched. By doing so, the Admin Control Center searches for the Sentinel protection key at a specific address, which is much faster. |
| Problem | You receive an error message indicating that Sentinel License Manager was not found. |
| Solution | The error message might be for one of the following reasons: >Sentinel License Manager was not loaded. Try restarting Sentinel License Manager in the Windows Services window. >There is a communication error with the machine on which the Sentinel protection key is located. If you repeatedly receive the error message, try using a different search mechanism. |
| Problem | You cannot add files when using the Sentinel LDK Data Protection utility. |
| Solution | The problem may occur for one of the following reasons: >You are attempting to add a list that includes problematic files. Remove all problematic files marked in red in the File list. >You are attempting to add a file that is outside the scope of the filters defined in Sentinel Envelope. You must protect your software again using the new file filter settings. >For additional information, see Protecting Data Files. |
| Problem | When using Sentinel LDK Data Protection utility, you receive a message that no data filters were defined for a program in a Sentinel Envelope project. |
| Solution | The problem cannot be solved using the Data Protection utility. You need to use Sentinel LDK Envelope to protect your software again, and to specify file filter settings. |
| Problem | When running a protected Java application, error code 22 is thrown. |
| Solution | When a java application is protected using both Sentinel LDK Envelope and Sentinel Licensing API, the JAR files used by the protected application must have the same version number. Ensure that you are using both Sentinel LDK Envelope and Sentinel Licensing API from the same version of Sentinel LDK. |
| Problem | When you are logged in to both the Vendor Portal and the Customer Portal simultaneously in Sentinel EMS in different tabs of a single Web browser instance, a message for an internal error is generated. |
| Solution | To work simultaneously with the Sentinel EMS Vendor Portal and Customer Portal on a single machine, use two separate Web browser instances. |
| Problem | When you download a C2V file (for example, abc.C2V) from Admin Control Center using the Safari Web browser, Safari appends '.xml' to the file name (for example, abc.c2v.xml). As a result, Sentinel EMS blocks the file. |
| Solution | Before you attempt to use the C2V file in Sentinel EMS, remove the '.xml' extension from the file name. |
| Problem | When an application call a Sentinel EMS Web Service, error 403 is returned. |
| Solution | HTTP verb tampering is an attack that exploits HTTP verb-based authentication and access control mechanisms. The vulnerability lies in the configuration of the security constraints that specify HTTP verbs that often allow more access than intended. An application's authentication and authorization mechanisms can be bypassed with HTTP verb tampering when the security control fails to block verbs that are not listed. Effective with version 7.9, Sentinel EMS Web Services have been modified to prevent HTTP verb tampering. The methods that are used to call Web Services have been whitelisted: GET, POST, DELETE, PUT. When calling these methods in your application, you must ensure that they are written using only upper-case letters as shown here. Variations that used lower-case or mixed-case letters have been blacklisted. This is a standard practice as suggested by the Internet community and is mentioned in RFC standard protocols (RFC 7230 and 7231). The use of method calls that do not comply with these practices will cause your application to fail with error code 403. |
| Problem | Given the following situation: You call the GetInfo function in the Sentinel Licensing API to fetch the fingerprint for an SL UserMode key. The fingerprint that is retrieved resembles the following: This indicates that the API function retrieved an empty fingerprint. This occurs when the SL UserMode license cannot be accessed or is corrupted. |
| Solution | The most common reasons for this issue is that access to the directory that contains the SL UserMode licenses is denied. When you resolve the access permission issue, the API function will be able to fetch the fingerprint as required. If the problem is not caused by access permissions, the most likely cause is that the SL UserMode licenses have become corrupted. To resolve this issue, you must clear the entire SL UserMode license directory. As a result, all locked licenses will be invalidated due to clone protection. It will be necessary to reissue these licenses. Unlocked licenses can be reinstalled in the directory. For information on the location of SL UserMode licenses on the user’s machine, see Viewing License Updates. |
This page is related to key-based licenses — a regular license type used in TestComplete 14.93. For information on the new ID-based license type, see SmartBear ID-based Licenses.
TestComplete uses the Sentinel LDK License Manager service to activate licenses and to manage and verify license information. If the service is not running, TestComplete cannot check it and therefore cannot start, or, if the license has not been activated yet, it cannot complete the activation. The service is started automatically after TestComplete is installed and automatically starts every time the operating system loads. You receive this error message because the service is stopped or is not running properly.
To ensure that the Sentinel LDK License Manager service is running:
Open the Windows Control Panel > Administrative Tools > Services applet.
Select the Sentinel LDK License Manager service in the list.
Right-click the service and select Start or Restart from the context menu.
Once the service is running, click Try Again to close the message box.
If the service does not start or if it is not in the list, do one of the following:
Reinstall the HASP drivers that are used to manage and verify license information.
See instructionsSee instructionsGo to the link:
Download the provided file.
Extract all files from the downloaded archive.
Launch the Windows command prompt with administrator permissions and type the path to the haspdinst.exe (or hasplms.exe) file that is located in the previously unpacked folder.
Specify
-r -kpas parameters and execute the command to remove the HASP drivers.To install the HASP drivers, rerun the previous command with the -i argument instead of -r-kp.
Reinstall TestComplete.
Resolve the problem by using the Licensing Troubleshooter on our website.