000025410 - How to resolve 'Bad String' errors when running RSA ClearTrust installation shell script on Sun Solaris

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000025410
Applies ToRSA ClearTrust 5.5.3
Sun Solaris 2.9
IssueHow to resolve "Bad String" errors when running RSA ClearTrust installation shell script on Sun Solaris
When running RSA ClearTrust installation shell script on Sun Solaris, a user is prompted to type "yes" to accept the license agreement. After typing "yes", the following messages appear in the console:

Bad String
Invalid response.  Type "yes" or "no" to continue.

The same messages appear when the user tries to retype a correct response.
CauseThe RSA ClearTrust installation shell script invokes the Sun Solaris pkgadd utility to install ClearTrust. By default, the pkgadd utility relies on the truncate routine located in /usr/bin to function. On some Solaris systems, /usr/bin/tr may be incompatible with pkgadd routine.
ResolutionWorkaround 1: temporarily rename the "tr" within /usr/bin and create a symbolic link to /usr/ucb/tr using the following command:

    # ln -s /usr/ucb/tr tr

This configures the pkgadd utility to utilize the truncate routine within the /usr/ucb location. After this symbolic link is created, the shell script will function correctly and the user will be able to accept the license to allow RSA ClearTrust installation to complete. Users can restore the original version of the truncate utility to /usr/bin by removing the symbolic link.
Workaround 2:

Check the value of the LANG environment variable. If the configured charset isn't actually installed on the system, you might obtain the error message mentioned in here.

As a workaround simply unset he LAN variable before running the installer. This can be done with the following command (sh):

unset LANG

... and then running the agent installer from the same shell.

If this workaround does not work, please see workaround 1.
Legacy Article IDa29539