Troubleshooting and FAQs

Question: For successful communication between the RMS License Manager and its clients, are there any requirements regarding the MTU limits?

Generally, the MTU value should be set to 1500. Starting RMS 9.8.1, the license packet size has increased due to change in the encryption algorithm. The table below describes the related changes and recommendations:

Release Maximum Size of the License Packet (bytes) SDK Features Impacting Packet-Size
Prior to v8.4.1 1432 bytes (RMS payload is 1420 bytes) Vendor information limited to 395 bytes in long licenses. Due to large software vendor information support, the license packet size has increased.
Post v8.4.1 7512 bytes (RMS payload is 7500 bytes) The private and public software vendor information can be up to 2000 and 395 bytes, respectively, in long licenses.
Post v8.6.1*

Dynamic packet size

1432 bytes (RMS payload is 1420 bytes)

Vendor information limited to 395 bytes in long licenses
Dynamic packet size
7512 bytes (RMS payload is 7500 bytes)
When Vendor information ranges from 395 to 2000 bytes in long licenses
Post v9.8.1 13012 (RMS payload is 13000 bytes) Introduced a new industry-standard RSA algorithm to secure the RMS License Manager communication.
Recommendations for Successful Communication

Follow the recommendations below for successful communication between RMS client and License Manager:

>The MTU value should be set to 1474 or above.

>For larger packets (when software vendor information is specified up to high limits, larger than the MTU size), packet fragmentation must be allowed.

>If you experience communication problems, you may diagnose your network using the following command:

> Prior to RMS SDK v8.4.1: ping –l 1500 <machine -name>

>Post RMS SDK v8.4.1: ping –l 7554 <machine -name>

*Starting version 8.6.1, the License Manager and client library support dynamic packet size.

Question: Does industry-standard RSA algorithm has an impact on Standalone Licensing Library?

In earlier releases, standalone licensed application used the proprietary encryption algorithm while communicating with the in-process License Manager. Starting v9.8.1, standalone licensed application will not use any encryption for this communication.

Question: How many license codes can be written into a license file? Is there any format for the license codes?

A license file can contain as many license codes as you want, from the same or different vendors.

Below are the conventions for the license file:

1.No more than one license code can be specified on one line of a file.

2.All characters in a license code must be 7-bit ASCII. This means no double-byte characters or accented characters may be used.

3.A single license code cannot be split across lines.

4.A license code must be terminated either by a new line or a pound sign (#). If a pound sign (#) is present on a line, all characters following it (until a new line) will be treated as a comment and ignored. Comments may appear anywhere in a license file.

Question: What will happen when the maximum size of the usage and the trace files are reached?

Refer to "Managing the Size of the Usage Log File" in the Sentinel RMS SDK System Administrator Guide.

Question: How many feature-version combinations can be listed in the license table?

2000 feature-version combinations can be listed.

Question: What is the difference between an additive and exclusive trial license?

Failover is not provided by an exclusive trial license. Whereas, the additive trial licenses provide automatic switchover to the next available license.

Question: Let us assume that an application is running in standalone mode and after that the user adds a license to the license file. Can the application use this license?

No. The application loads the license file (containing all licenses) when it is started. To use the licenses that are manually added after the application is started, you must restart the application.

Question: Let us assume that the License Manager is running on a network and the user adds a license to the license file. Can the application use this license?

No. The RMS License Manager loads the license file (containing all licenses) when it is started. To use the licenses that are manually added after the License Manager is started, you must restart the License Manager.

Terminate User Session

Question: Is it possible to terminate active user session for isolated License Managers?
Yes. The only exception is that if the License Manager is running as a service on Windows OS, you will not be able to terminate active sessions.

Question: Can I terminate active sessions for both old and new clients?
Yes, both old and new clients are supported. A session created using either Unified or Traditional API can be terminated by calling the API function.

Question: For all clients, what happens when the client application is restarted?
After termination of active user sessions, when the client application is restarted it should work similar to the way it was working prior to termination.

Question: Does RMS allow termination of detached/commuted or repository license sessions?
No.

Question: Does RMS allow termination of sessions for capacity licenses?
No.

Question: Explain the behavior when active sessions (for redundant licenses) are terminated for clients prior to RMS v9.6?

Post termination of active user sessions, refresh calls from the client application to the License Manager may result into the SNTL_SUCCESS or SNTL_REMOTE_UPDATE error code. This is applicable to RMS v9.5 or earlier.