Recognizing Issues Related to Battery Depletion in Sentinel Vendor Keys

Sentinel Master keys and Sentinel Vendor keys contain a real-time clock that is used to synchronize exchanges of information with SafeNet and for time-based license modules that are stored on the keys. The battery on these keys can become depleted after 7-10 years. This document describes the symptoms and indicators of a depleted battery on one of these keys and how to proceed in the event this issue occurs.

Indications of the Issue

If the battery on the Master key or Developer key is depleted, following indicators can be observed :

  1.  Using Sentinel License Generation API – When you attempt to perform an action that requires access to the time-based licenses in the Master key, the action will fail with the return code: SNTL_LG_MASTER_NO_BATTERY_POWER (5045).
  2. Using Sentinel EMS – When you attempt to perform an action that requires access to the time-based licenses in the Master key, the action will fail as described below
    • When the Trialware module, Unlocked Licenses module or V-Clock module is accessed, the following error message is displayed: “The battery in the Master key is depleted”
    • When the Reporting module is accessed (in Sentinel LDK 7.3 and earlier), the following error message is displayed: “Custom reports cannot be used. Either the Master key is not connected or the required license for this feature does not exist on the Master key”
    • When you attempt to issue an update for a Sentinel protection key, the following error message is displayed: “You cannot generate an update for this Sentinel protection key. The battery in the Master key is depleted”

 3. Sentinel LDK Envelope – When you attempt to protect an application that uses AppOnChip, the following warning message appears in the log file at the bottom of the screen: “The connected Sentinel Vendor key does not contain an AppOnChip license module. Your protected application will not work with Sentinel HL Basic and Pro keys”