Troubleshooting and FAQs

Question: Can RMS SDK components be installed on localized operating systems?
The Internationalization support is expanded in this release to cover all the localized versions of Microsoft® Windows®. This support is applicable to the RMS SDK client libraries and License Manager so that these components can be installed on any non-English operating system and run from any localized path complying to UTF-8 encoding on Microsoft Windows.

NOTE   Prior to the v8.5.2 release, the support was limited to double-byte compliant systems.

In the v8.5.2 release, the following exceptions were noted:

>A localized path cannot be specified using any RMS API, environment variables, and various tools and utilities.

>The Custom installation option for the RMS SDK cannot be used on non-English operating systems. However, installation on the default path can be done successfully.

>The localized user and host names are not supported for usage logging, locking, and in group reservation files.

NOTE   In the license_info_struct, a new member "license_storage_unicode" is added that will obtain the localized path by converting its value to wide char using the Windows API, MultiByteToWide Char. Use of this field is recommended to facilitate Internationalized applications.

Question: Why do I get the "checksum error" while trying to extract the RMS SDK components on HPUX and AIX ?
To resolve the checksum error, use the GNU tar to extract the RMS SDK components. This problem occurs on systems where the native tar utility does not support long file names.

Question: List down the new 64-bit tools/utilities and library that has been introduced in RMS v9.6 for Mac OS?

The following table provides the list of 64-bit tools and libraries introduced in Sentinel RMS v9.6 for Mac OS.

Tools (64-bit) Vendor Tools (64-bit) Static Library (64-bit)
echoid64 vusage64 libclean64.a
echouid64 lsclean64  
lcommute64    
lsdecode64    
lslic64    
lsmon64    
lspool64    
lsrvdown64    
lsusage64    
lswhere64    
rcommute64    
rlftool64    
ulsdcod64    

Terminate User Session

Question: Is it possible to terminate active user session for isolated servers?
Yes. The only exception is that if the server is running as a service on Windows OS, you will not be able to terminated 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 session(s), 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. Currently, we are not supporting this.

Question: Does RMS allow termination of sessions for capacity licenses?
No. Currently, we are not supporting this.

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

Post termination of active user session(s), refresh calls from the client application to the License Manager will result in either SNTL_SUCCESS or SNTL_REMOTE_UPDATE error code. This is applicable to RMS v9.5 or earlier.