Sentinel LDK and Sentinel HASP Run-time Environment ... - Uwerk.de

Sentinel ® LDK and Sentinel HASP ® Run-time
Environment Installer GUI: Readme
Installer Version 6.5
Package Version 6.5
September 2012
This document provides information regarding the Run-time Environment Installer GUI for Sentinel LDK and Sentinel
HASP, including supported operating systems, enhancements, known compatibility issue, and issues resolved.
("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 2008 R2
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 GUI detects the version of the operating system during Run-time Environment installation, before
installing the relevant drivers.
By default, Windows 7, Windows Vista, and Windows Server 2008 (R2) 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 GUI to upgrade the 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, it does not terminate running services. For example, if the
Sentinel License Manager is running as a service, you must stop the service before upgrading the Run-time
Environment.
Compatibility Issues

Run-time Environment may be incorrectly reported as a virus by Control Guard Agent version 4.0.0.27. If this
occurs, update to a later version of Control Guard Agent.
Run-time Environment may be incorrectly reported as a virus by SkyRecon StormShield Agent version 5.6. If
this occurs, contact SkyRecon support to determine if a fix is available.
Issues Resolved in This Release
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 a specific machine 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.”
99350: On the Mac OS 10.6 Server with 64-bit kernel extension: The Run-time C samples (static, shared,
Xcode static and shared) sometimes stop responding after displaying the copyright notice.
Workaround: Install the latest operating systems updates (10.6.8 or later) from Apple.
Note: If the precompiled Run-time sample binaries do not function properly (they do not respond when
executed), recompile the binaries with Xcode or GCC.
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.
140898: Under the Linux operating system, Sentinel License Manager does not support the IPV6 network
protocol.
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.
170463: When the user attempts to install MicroSoft Office 2010 on a computer that contains the Run-time
Environment, the installation fails and displays the following error:
Error 1406. Setup cannot write the value Assembly to the registry key Software\Classes\CLSID\{0006F024-
0000-0000-C000-000000000046}\InprocServer32\14.0.0.0.Verify that you have sufficient permissions to
access the registry or contact Microsoft Product Support Services (PSS) for assistance.
Workaround:
Disable the License Manager,install Microsoft Office, and then re-enable the License Manager as follows:
1. Start the Registry Editor (Start > Run > Enter Regedit.)
2. Go to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aksfridge"
3. Change the value of "Start" from 2 to 4.
4. Restart the computer. (The License Manager is disabled.)
5. Install Microsoft Office.
6. Start the Registry Editor.
7. In the key described above, change the value of "Start" from 4 to 2.
8. Restart the computer. (The License Manager is enabled.)

¡ ¢£¤¥¦§¨ © ¨ ¤¥¦§¨ ¤¤
DocID 118f Revision 1209-1