Use the information in this chapter if you run into problems installing Rational Suite. The following areas are covered in this chapter:

• Troubleshooting the Installation of Rational Suite (UNIX Components)
• Troubleshooting the Installation of Rational Suite (Windows Components)

Contact Rational Technical Support if you are unable to resolve your problems or if you have questions regarding the installation, use, or maintenance of this Rational Software product.

Error messages are shown in bold italics in this section.

If you are having problems with the display showing strange characters on your screen and your screen does not clear for each new menu, you may have your TERM environment variable set incorrectly. Try setting it to something else like xterm, vt100 or ansi. To prevent the program from using escape sequences to do underlining, run the programs with the -no_underlining (alias -nu) option. This will prevent the commands from using escape sequences.

If uninstalling something fails, it may be that you are not the original installer. Log in as the person who installed the product and rerun the uninstall script as that person.

If you have problems creating directories, it may be that you do not have the correct permissions. Check your login name and the groups you belong to using the UNIX id command. Check the directory permissions of the directory where you are trying to create a directory. You must have read (r), write (w), and execute (x) permissions for you or the groups you are in.

If you have permission problems with the tar command, it may be that you are trying to install on top of an already existing product. In most cases, this type of error can be ignored.

If you run out of disk space while installing products, you cannot ignore this problem. The best thing to do is uninstall the Suite and reinstall it in a place where you have sufficient space to do the installation. Disk space requirements are summarized in Rational Suite (UNIX Components) Installation Requirements. The approximate amount of disk space you need to install the Suite is also provided in the Product Customization Menu when you run the rs_install command.

Check that you have correctly mounted the CD-ROM. Refer to Accessing the CD-ROM Drive. Make sure that you are running the installation commands from the CD-ROM directory. There must be an extras directory in the same location. The command looks for the installation data in there. If you have mounted the /cdrom directory from another system, make sure the directory has been properly exported - it needs to be listed in the filesystem table for exported file systems. This file is operating-system dependent.

This means that the installation was trying to untar this file. In doing so, it expected it to create a directory structure that looks something like releases/product.ver/install. It could be that the tar command failed due to lack of disk space, or you do not have permissions to read the file. Check to see if you can untar the file that is shown by doing a tar -tf <file0> where <file0> is the full path to file0.

This means that the install could not find a tar file in the listed directory. It could be that you are trying to install a Solaris CD-ROM on a non-Solaris system or an HP-UX CD-ROM on a non-HP-UX system.

or

This means that the license keys in the license file do not match and are inconsistent with the text of the license. The licenses consist of several parameters and a 12-digit hexadecimal key that was created using these parameters. The parameters are in ASCII text but they cannot be changed or it will invalidate the license. The parameters used to create the license are the server host ID, license name, vendor daemon name, expiration date, number of users (quantity), VENDOR_STRING, OVERDRAFT, SUPERSEDE, DUP_GROUP, and NOTICE.

This means that there is a problem with the license server. It could be that:

1 The license server was never started.

2 The license server failed to start. This happens when the license keys are inconsistent.

3 There is already a license server running but it is not using the Rational Suite DevelopmentStudio license file.

Check the license server log file which is kept in /rational_dir/config/server-name.log.

This could mean that multiple Rational servers are running, or a stale lock file was not cleaned up. This error could result from either:

1 Another copy of lmgrd is running.

2 A prior lmgrd was killed with kill -9 which would leave the vendor daemon running.

To correct this, kill the lmgrd and rational processes and remove the Rational lock file:

a Use the ps command or equivalent to find the process IDs:

ps -ax | egrep "lmgrd|rational"

b Kill those processes:

kill Process-ID-of-lmgrd Process-ID-of-rational

c Remove the lockrational file which can be found at either:

/usr/tmp/lockrational
or
/tmp/lockrational

Run /rational_dir/config/start_lmgrd_on_machine

It may be that the license server is not the same system on which you are installing. You must have remote shell access (rsh or remsh) to the license server system.

It may be that the license server is not the same system on which you are installing. If so, it must run the same operating system that the product you are installing requires.

If the license server is not the same system on which you are installing, it must have access to the rational_dir directory where Rational products have been installed.

The lmhostid command failed. Check to see if the lmhostid command shown will run on your local host. If so, enter the host id number in the License Server Host ID Menu (choice number 2).

There was a problem accessing the rational_dir directory or the lmhostid command was not installed from the CD-ROM.

This means that the host ID number will not work. Check again using the lmhostid to see what the host ID is. It should be at least four or more hexadecimal digits.

or

If you entered a port number and it appears that the number is in use in your /etc/services file or under NIS services, you may have a problem with licensing. Rational products use FLEXlm which uses TCP/IP sockets to communicate with a license server using a specific port number. This port number is specified in the license file on the SERVER line. The license server will not be able to open a socket on a port that is already in use. Rational recommends that you use the default port number, 27000.

This means that the import file you specified contains INCREMENT lines but none of them match the two that are expected. Make sure that the file you import contains one or both of these licenses.

This means that you only have a license to use Rational Suite DevelopmentStudio (UNIX Components). If you are not using the unlicensed product, no action is necessary. If you plan to use the Windows Components, request a Rational Suite DevelopmentStudio (Windows Components) or a Rational Suite DevelopmentStudio RealTime (Windows Components) license from AccountLink.

If you see this message when you run start_lmgrd, remove the ulimit command from the script.

If you have problems installing the Web Interface components of Rational Suite, try the following suggestions before you call Rational Technical Support:

• Be sure to stop all applications before you begin the installation.
• Turn off all virus protection software. These programs often run in the background and interfere with the installation and file decompression process.
• Turn off any user interface managers or desktop environments that run on top of Microsoft Windows.
• Disable video features such as virtual screens or screen switching.
• Change to a standard mouse driver, or disable special mouse features that perform tasks such as leaving pointer trails or Support Information

The lmtools application is available on Windows and is designed to help diagnose licensing issues. Rational installs this application with all products in the rational_dir\common directory. If the license server is installed, click Start > Rational License Server > License Tools. For more information about using this diagnostic tool, see the FLEXlm User Guide. You can access this guide online by typing rsdsu_help.