We are pleased to announce the availability of the latest Sentinel HL Upgrade tool.

This tool allows ISVs to upgrade Sentinel HL keys in Hardlock configuration to Driverless configuration. Customers can then integrate their software with Sentinel LDK protection and licensing and benefit from the numerous advantages this platform offers compared to legacy Hardlock keys.

The new tool can be downloaded from Sentinel Customer Community.

 In case EMS in LDK 7.3 does not work after Java 8 upgrade , it can be resolved by following steps mentioned below :

• Open SentinelEMSw.exe located at ....\Program Files \Sentinel EMS\EMSServer\bin 
  • Now click  "Java" tab and ensure JVM dll should point to JRE 8’s jvm.dll.
• Browse to  ….\EMS_HOME\EMSServer\bin  from command prompt opened in Run as Administrator mode.
• Execute “service.bat remove” and then “service.bat install”.
• Open services.msc and select properties "Sentinel EMS" , change the services Startup type to "Automatic".
• Restart EMS Service.

• The Sentinel RMS License Manager cannot function properly if machine name contains all numeric characters.
• In case of Microsoft Windows Operating System, the Sentinel RMS License Manager is installed successfully and Sentinel RMS License Manager service also runs fine. However, if the port number details are checked through netstat –ano, it is observed that UDP port 5093 and does not mention RMS License Manager Process ID.
• For Linux OS, running lserv from terminal does not start Sentinel License Manager.
• When machine name contains only numeric characters(ex:1234), this behaviour is seen as Sentinel RMS License Manager uses C API “gethostbyname()” which cannot pass only numeric characters as host name.
• It is recommended to use alpha-numeric machine name.

For Envelope protected applications, RUS package is embedded in the protected apk file. 

When the protected application is executed for the first time, it searches for the license.

If no license is found then it opens up the RUS functionality and License can be activated using following options:

1) Product Key: This option displays Online Activation screen where server details and the product key needs to be provided.This method requires active data connection on the device

 2) License File: This is for offline activation using V2C file which has following options :

•   Collect Information: This is to collect the c2v file. which will be saved as “storage/sdcard/request.c2v”
•   Apply update: This will search and apply the v2c file from “storage/sdcard/”

Following are a few recommendations while protecting dll files in a web application using Envelope:

1. Change the ‘Message output mode’ to ‘eventlog’ or ‘standard error log’:

The ‘Message output mode’ in envelope is set to ‘window’ by default. In case a web application hosted on servers such as IIS, tries to display error through a dialog box, the server returns the error message ‘Unable to load modal dialog box’.

So, it is recommended, to change the message output mode to ‘eventlog’ or ‘standard error log’.

2. Copy supporting files in System32 or any other %PATH directory:

When a protected method is called, sometimes the running process (server exe) is unable to locate the supporting files that are present with the protected dll and the web page does not load as it is still searching for the supporting files. This leads to ‘request timeout’ error as the files are not found.

It is recommended to copying the following files in System32 or any other %PATH directory-

• hasp_rt.exe
• hasp_windows_xxxxx.dll
• hasp_windows_x64_xxxxx.dll
• haspdnert.dll
• haspdnert_x64.dll

3. Using different feature id at global and feature level:

In case same feature is used for global and method level login then by default, the license checking frequency is set to ‘Once per program’ .Hence license will be checked only for the first time protected method is called.The license will not be checked again until the server is restarted.

 To overcome this, it is recommended to use different feature id’s for global and feature level login.Using a different feature id will allow us to set the frequency to ‘Everytime’ and hence license would be checked everytime a protected method is called.

The error "H0698" implies Functionality is unavailable .This  error can be resolved by re-protecting the application using the LDK 7.3 envelope and its components along with hasp_rt.exe.

LDK 7.3 is available for download at Sentinel Customer Community

This error can be resolved by creating a registry entry for EMS: 

1. ​Open the Registry Editor and browse to  "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Aladdin Knowledge Systems\HASP SRM Vendor Suite\General"
2. Set the string value "Login Remote" to"true". Create this string value if not existing
3. Restart the Sentinel EMS service
4. Now open the Master Wizard- "Server Address" field should be editable now
5. Instead of machine name, enter Server IP Address in "Server Address"
   Now the master wizard should be able to login successfully.

Please ensure to create a System Restore point before editing registry.

This error is displayed when the Master database file (.MDF) is present at following location :

../Program Files/Microsoft SQL Server/ directory

Removing the MDF file from this location should solve the issue. 

In case it throws another error "Database Already Exist" then follow these steps-

1. Login to SQL Instance from SQL Management Studio using 'sa' as username

2. Check if a new database can be created

• If yes- then there is no problem on SQL part
• If no- then check permissions for user sa or else proceed with the error displayed while database creation.

3.  Check EMS installer log for any error in installation directory.

4.  If installer logs are not created or there are no fresh entries then this issue might be related to JAVA

5. Check if supported version of JAVA is installed and reset the values in 'Jre_HOME' and 'path' environment variable

Try running the EMS installer once again, this should work fine now.

The Sentinel Protection Installer is an integrated installer of Sentinel System Driver and Sentinel Protection Server.

Enhancements:

• Supports Macintosh OS X 10.10 (Yosemite).
•  Auto launch of Sentinel Server on Mac OS X 10.10 (Yosemite) at boot time.

Sentinel Protection Installer 7.4.2  for Sentinel UltraPro keys on Macintosh is now available at Sentinel Customer Community.