Resolved Issues
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-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 |