Resolved Issues
Service Pack: 8.4.001
The following issues that were reported by vendors were resolved in this service pack.
| Reference | Resolved Issue | Components |
|---|---|---|
| SM-125689 |
After upgrading Sentinel LDK-EMS to version 8.4, some vendors were not able to burn HL keys or use online activation when working with older versions of the Run-time Environment. |
Sentinel LDK-EMS |
| SM-122350 |
Resetting a password in Sentinel LDK-EMS would sometimes fail with the error message: JSON parse failed. Unexpected end of JSON input |
Sentinel LDK-EMS |
| SM-122158 |
Given the following situation: 1.The vendor runs the Master Wizard to generate customized RTE installers. 2.In the Wizard, the vendor selects Use SSL and specifies port 443 or they clear Use SSL and specify port 80. 3.After installing the customized Run-time Environment, the vendor or one of the vendor's customers attempts to burn an HL key or use online activation with Sentinel LDK-EMS. Sentinel LDK-EMS is unable to update the HL key or SL key. |
Master Wizard |
| SM-125738 |
Given the following situation: 1.A user's login name for the computer contains Chinese characters. 2.The user introduced a Master key using the Master Wizard. The Master Wizard did not generate the haspdinst_vendorId.exe and haspds_windows_vendorId.dll files for installing Sentinel LDK Run-time Environment. |
Master Wizard |
Release: 8.4
The following issues that were reported by vendors were resolved in this release.
| Reference | Resolved Issue | Components |
|---|---|---|
| SM-114671 | Sentinel LDK Developer key was not recognized by Envelope engines (.Net, Java, WinNG). | Envelope-Win, .NET, Java, NG |
| SM-114470 | Chinese characters were garbled in an Envelope error message. | Envelope-Win,.NET |
| SM-114462 | .NET Envelope would fail to protect certain DLLs. | Envelope-.NET |
| SM-114908 | .NET Envelope: Invalid VAR opcode: ldelem msg on terminal . | Envelope-.NET |
| SM-112663 | Envelope cannot open project file under a Chinese version of Windows after the Chinese language pack is installed. | Envelope-GUI-Win |
| SM-112703 | Envelope would fail when adding a .NET Core application with dependencies that use a lower version than exist in the project. | Envelope-.NET |
| SM-112829 | A debugging log would be included in envelope.com during protection of a .NET application. | Envelope-.NET |
| SM-111408 | Under poor network conditions, an Envelope grace message is not shown when expected. | Envelope-.NG |
| SM-118496 | Under certain circumstances, when adding a DLL assembly to Envelope, an unsupported .NET assembly error (2012) is generated. | Envelope-.NET |
| SM-113922 | Under certain circumstances, using Web Services to perform a product key update would fail with the following message: 400 Bad Request The input XML is not valid. Node - com.sfnt.ems.domain.ProductKey. |
Sentinel LDK-EMS Web Services |
| SM-114383 | After disabling an entitlement in the Entitlement table, there was no visible indication that the entitlement was disabled. | Sentinel LDK-EMS |
| SM-111256 |
After you upgraded to the latest version of Google Chrome or to Microsoft Edge version 95 or later, functionality related to protection keys was blocked if you accessed Sentinel LDK-EMS using HTTP mode. This applied to both the vendor portal and the customer portal. |
Sentinel LDK-EMS |
| SM-119586 |
After connecting to a VPN, when you click Submit on the Access to Remote ACC panel, a false-positive warning similar to the following was sometimes displayed: "A duplicate License Manager ID exists on this server and on the server at address 10.42.49.253. This is typically caused by cloning a VM. Licenses on these two servers may be inaccessible" |
Sentinel License Manager |
| SM-119327 |
If no host is specified, AdminAPI uses "localhost" to connect to the License Manager. But in modern machines, localhost is resolved to "::1". This may not work because the IPv6 option may be disabled in the License Manager. AdminAPI now uses "127.0.0.1" instead of "::1". |
Sentinel Admin API |
| SM-115393 |
When the client identity is installed in Admin Control Center, and the License Manger received a detached license from a remote machine, a local API was affected by the local License Manager detachable configuration. However, the local License Manager should have only acted as the forwarder in this case. |
Sentinel License Manager |