![]() ![]() On the Sessions page in Sentinel Admin Control Center, Key information was incorrect and Location information was missing. ![]() As a result, Sentinel LDK Cloud Portal did not show correct product names after Docker instance was restarted. Product names were not stored in the database, but were stored in lic_name.dat. As a result, the LMS regards the request as coming from different machines, and more seats were incorrectly consumed. When using the GCP load balancer, it uses multiple instances to dispatch a runtime API request to the LMS. ![]() When calling the applyV2C function of the Cloud Portal service, the MEM usage of the License Manager container continuously increased, forcing the License Manager to restart. Issues Resolved in Version 8.52 Reference No enhancements are included in this release. Issues Resolved in Version 8.53 Referenceġ.The vendor asssigned multiple key IDs in the Limit to Key ID field for a client identity on the license server.Ģ.The vendor sends the identity string for the client identity to the licensed user.Īfter the licensed user applies the identity string on their machine, only one key ID is shown on the user's machine. Sentinel LDK Run-time Environment and protected applications are both supported under Windows 10 22H2. This topic contains the revision history of enhancements and issues resolved in Sentinel LDK Run-time Environment for Microsoft Windows. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |