Sentinel^® LDK and Sentinel HASP^® Run-time Environment Installer API and Sample: Readme

Installer Version 6.56

Package Version 6.56

March 2013

This document describes the API and samples for the Run-time Environment Installer for Sentinel LDK and Sentinel HASP, including supported operating systems, enhancements, installation and upgrade notes, and issues addressed. ("Sentinel LDK" is the next generation of the Sentinel HASP system.)

Operating Systems Supported

• Windows XP (32-bit and 64-bit)
• Windows Server 2003 (32-bit and 64-bit)
• Windows Vista (32-bit and 64-bit)
• Windows 2008 (32-bit and 64-bit)
• Windows 7 (32-bit and 64-bit)
• Windows 8 (32-bit and 64-bit)
• Windows 2008 R2
• Windows Server 2012

Note: Windows XP Embedded is not supported with this installer. To install the Run-time Environment under Windows XP Embedded, use akshasp.sld. This file can be found under \Runtime Environment\win_xp_embedded\ in your installation of Sentinel LDK or Sentinel HASP.

Changes in Terminology

Sentinel Admin Control Center user interface and help files incorporate changes in terminology as follows:

• The Sentinel HASP product is now referred to as Sentinel LDK.
• SL keys that were created with Sentinel HASP Business Studio now appear in the user interface as "SL-Legacy" keys.
• References to Sentinel EMS in the help files are also valid for Sentinel HASP Business Studio.

Installing the Run-time Environment

• The Installer API detects the version of the operating system during Run-time Environment installation, before installing the relevant drivers.



• By default, Windows Vista (and later) operating systems display a User Account Control message during driver installation. The user must click Continue to continue the installation. Alternatively, the user can change the default setting from the Control Panel of their operating system.

Upgrading the Run-time Environment

When using the Installer API to upgrade the Sentinel LDK Run-time Environment, ensure that:

• No other Run-time Environment Installer is active.



• No other Run-time Environment components are active. Although the installation program terminates applications that are accessing the Run-time Environment, it does not terminate running services. For example, if Sentinel License Manager is running as a service, you must stop the service before upgrading the Run-time Environment.

Compiling the Sample

Two compilation samples are provided. Use the compilation instructions relevant to your operating system.

The Run-time Environment API must be built with Microsoft Visual Studio 2005.

1. Open a command prompt.
Set the environment path by running vcvar32.bat.
2. Run mkx86.bat.

1. Open the Microsoft Visual Studio 2005 x64 Cross Tools Command Prompt.
2. Run mkx64.bat.

Accessing Admin Control Center in Internet Explorer Metro Mode

Under Windows 8, Internet Explorer 10 can be operated in "desktop" style or "Metro" style. When users attempt to access Admin Control Center for the local License Manager in the Metro style browser, they get the message "This page can't be displayed". (This problem does not occur when a user attempt to access Admin Control Center for a remote License Manager.)

To access Admin Control Center for the local License Manager under Windows 8 with Internet Explorer 10, the user must do either of the following:

• Operate Internet Explorer in desktop style:
  
  
  1. After you receive the message "This page can't be displayed" in Metro style, click the wrench icon at the bottom right of the browser window.
  
  
  
  2. Click View on the desktop. Admin Control Center is displayed.


• Enable Internet Explorer to access Admin Control Center in Metro style:
  
  
  1. After you receive the message "This page can't be displayed" in Metro style, click the wrench icon at the bottom right of the browser window.
  
  
  
  2. Click View on the desktop. Admin Control Center is displayed.
  
  
  
  3. Click the cogwheel ("Tools") icon at the top right of the browser window. From the menu, select Internet options > Security. Select the Trusted sites zone. Click the Sites button.
  
  
  
  4. "http://localhost" is already filled in. Click Add. Close the screen.

Compatibility Issues

• When Control Guard Agent version 4.0.0.27 is present on a computer, installation of the Run-time Environment will cause the operating system to crash. If this occurs, update to a later version of Control Guard Agent.



• When SkyRecon StormShield Agent version 5.6 is present on a computer, installation of the Run-time Environment will cause the operating system to crash. If this occurs, contact SkyRecon support to determine if a fix is available.

What's New in This Release?

• Windows 8 and Windows Server 2012 are now supported. The Run-time Environment is "Certified for Windows" by Microsoft for these operating systems.



• The command "haspdinst.exe -info" now retrieves the full version of the vlib.

Issues Resolved in This Release

• 170463: When the user attempted to install MicroSoft Office 2010 on a computer that contains the Run-time Environment, the installation would fail and display an "Error 1046" message.



• 185897: Run-time Environment v6.55 would not recognize a HASP HL key with Firmware v2.16. The key would not be displayed in Sentinel Admin Control Center.



• 186197: When an application is protected with "Enable data file encryption" selected in Sentinel LDK Envelope, and file extensions are added in the filter, it was not possible to save the encrypted files to a network location.

Issues Resolved in Version 6.55

• MKS177499: Under Windows 7 64-bit, protected application process would not exit from the Task Manager after closing.



• MKS180520: A Stop message (BSoD) would occur while running a DataHASP protected application when Norton Internet Security is installed.



• MSK79112: A delay would occur in obtaining the current remaining executions count when using the Licensing API hasp_get_sessioninfo() call soon after the hasp_login() call.



• MKS177029: The NX flag for hasplms.exe was not enabled.



• MKS178460: LM ID content of the LM Server whose information has not been refreshed for a long time would not be shown when more than 512 LM servers exist.



• MKS168507: If the HL key was changed while a machine was sleeping, then afterwards the License Manager would show that the original HL key is still present. The new HL key would not be recognized and would not work.



• MKS175770: hasplms.exe would crash and record an Access Violation error in the system log.

Issues Resolved in Version 6.50

• MKS160209: When installing the Run-time Environment under Windows Server 2008 x32 JP, the system would crash.



• MKS170889: Irrelevant "func_0" entries have been removed from the Admin Control Center access log.



• MKS167561: When using "Aggressive Search" in Admin Control Center, if you enter the machine's own name in the search parameters, the License Manager would fail to detect the local keys.
  

Issues Resolved in Version 6.27

• MKS159048, US159048 : SL licenses are now supported on dynamic disk.



• MKS153313: Under certain circumstances, when installing the Run-time Environment on a computer connected to a specific Fiber-Channel controller,  a Stop Error (BSOD) would occur.

Issues Resolved in Version 6.25

• US157306: Known compatibility issues are now listed in the Run-time Environment readme file.



• US126998, CASE1335: When the end user applied an update for one Product, multiple unexpected Products were added in the
Admin Control Center. In addition, when the ISV checked in a C2V file from the end user, duplicate Features relating to the Product were added in Business Studio.


• US150843, MKS132920: Expired detached licenses would continue to be displayed in Admin Control Center for 7 days. You can now customize Admin Control Center to display these licenses for 0 to 9999 days. In the hasplm.ini file, add or locate the parameter commuter_delete_days = and assign it the number of days to display expired licenses. If you specify 0, an expired detachable license entry is deleted within a few minutes after it expires.



• US148372, MKS142453:When a computer with an active protected application and attached HL was set to hibernate, and the HL key was then detached, the computer would freeze upon being restarted.



• US153304, MKS152843: An error would occur when running an RTE installer that includes a Provisional Product.



• MKS154755, 154375, 153944, 152449, US158710: hasplms.exe would fail, sometimes showing an Access Violation error in the system log.



• MKS147694: When a modification is applied to decrease the concurrency count, it was still possible to extend the duration of detached licenses even though the number of detached licenses exceeded the maximum allowed.



• MKS147644: The License Manager would lose track of the number of detached licenses for a given Product when a modification is applied to add a new detachable Feature.



• US144668: Under Windows XP, a protected application that is linked with Runtime API v.5.0, and is running in Run-time Environment v.5.95 or later would fail with "Communication Error 33" after several hours of activity.



• Ref #8033: If you attempted to update the Sentinel HASP Run-time, and your protected application uses DataHASP, it was necessary to close the protected application before running the update. (Resolved in version 6.22)



• MKS146944, 147038: The License Manager would eventually lose track of the number of detached licenses for a given Product if the number of available licenses for that Product was changed to a value lower than the number of licenses currently detached. (Resolved in version 6.23)

Known Issues - Runtime Environment Installer

• Ref#8475: When you attempt to integrate the Sentinel LDK Run-time Environment Installer MSM module in your Windows Vista installation package, a warning may be displayed. This is a known issue for the Installer, and the message can be ignored. For more information about this issue, go to this URL.



• MKS136831: Given the following circumstances:
  • A hasplms service exists in a location other than c:\windows\system32.
  • haspdinst is used install the Run-time Environment.
  haspdinst will copy the new hasplms.exe file to the standard location, but then start the old hasplms.exe.
  Workaround: Stop and remove the old hasplms.exe service before executing haspdinst.exe.
  (HASPUserSetup.exe and haspds.msm do not show this behavior. They always stop and remove a running hasplms service, then install and start the new one correctly.)
  This issue also exists in SRM 5.x and below.

Known Issues - Run-time Environment

• 12506: Sentinel LDK communicates via TCP and UDP on port 1947. This port is IANA-registered exclusively for this purpose. At the end user site, the firewall must be configured so that communication via this port is not blocked.



• 14827: Given the following situation:
  • A Product is protected by a Sentinel SL protection key and allows concurrency.
  • The number of concurrent users is the maximum allowed.
  Additional users attempting to access the protected software receive the message “Access denied” instead of the message “Too many users.”



• 137995: When a Feature that is disabled for virtual machines is accessed in a VM environment, the Run-time Environment returns the message HASP_FEATURE_NOT_FOUND instead of HASP_VM_DETECTED.



• 144293: In Admin Control Center, when the user clicks the Certificate button to display certificate information regarding an updated license, the certificate displayed is from the base version of the license. (This issue has no impact on license functionality.)
  This issue does not exist in Sentinel Admin API.



• 182646: After Windows 7 is upgraded to Windows 8, the user is not able to use existing SL licenses or to install new SL licenses.
  Workaround: After you upgrade from Windows 7 to Windows 8, reinstall the Run-time Environment.

Copyright © 2013 SafeNet, Inc. All rights reserved.