C H A P T E R  4

Troubleshooting

This chapter describes problems that can occur during Forte Developer 7 software installation and uninstallation.


Problem With Mounting the Product CD-ROM

If the product CD-ROM does not mount when you insert it in the CD-ROM drive, the installer does not start, and you cannot access the /cdrom directory. The
CD-ROM does not mount if the vold utility is not running. To start the vold utility, perform the following steps:

1. If you are not already a superuser (root), become a superuser by typing:

% su
Password: root-password

2. Start the vold utility by typing:

# /etc/init.d/volmgt start

The CD-ROM mounts and the installer starts.


Installing in a Directory Reached by a Symbolic Link

You can install in a directory where part of the path is a symbolic link. For example, if the default directory /opt does not have enough disk space, you can create a symbolic link of /opt that points to /export/opt. To prevent the installer from bypassing the symbolic link and installing in an actual file system, you need to complete the following workaround:

1. Become a superuser (root) by typing:

% su
Password: root-password

2. Save the existing symbolic link by typing:

# mv symlink temp

3. Make a new /opt directory which will serve as a mount point by typing:

# mkdir /opt

4. Mount the target directory so it is available as /opt by typing:

# mount -F nfs localhost:/directory/opt /opt

5. Install the product.

6. Unmount the target directory by typing:

# umount /opt

7. Restore the symbolic link that you moved in step 1.

# mv temp symbolic_link 

8. Exit from superuser privileges by typing:

# exit


Product Registry Problems

If you encounter installation or uninstallation problems that involve a corrupt productregistry file, you can sometimes use the Solaris Product Registry Tool to locate and fix the problem.

How Do I Identify and Fix a Failed Installation?

If some packages were not properly installed, you will have problems using the Forte Developer 7 software. For example, if you used the pkgadd command to install the software, you have corrupted the productregistry file. To verify whether all packages were installed properly, follow these instructions:

1. Become a superuser (root) by typing:

% su
Password: root-password

2. Open the Solaris Product Registry tool by typing:

% /usr/bin/prodreg &

3. In the left column of the tool, look at the list under the heading Registered Software.

If a yellow triangle is adjacent to the product name, then the product was not installed properly.

4. Select the product name, and then click the Uninstall button.

The Uninstall Failed dialog box opens.

5. Read the message in the box, and then click OK if you want to uninstall the product.

The Interactive Uninstall dialog box opens.

6. Follow the instructions in the subsequent dialog boxes until uninstallation is complete.

Once the uninstallation is complete, you can reinstall the product software using the product installer. See Chapter 2 for product installation instructions.

How Do I Fix a Failed Uninstallation?

If the uninstaller quits before all the product files are deleted, rerunning the uninstaller will not delete the remaining product files. The product files have been marked as deleted in the productregistry file, so the uninstaller does not remove the remaining files. To completely remove the product files, use the Solaris Product Registry tool, as described in the following procedure:

1. Become a superuser (root) by typing:

% su
Password: root-password

2. Open the Solaris Product Registry tool by typing:

# /usr/bin/prodreg &

3. In the left column of the tool, select all product names containing S1S7 or Forte Developer 7, and then click the Uninstall button.

The Uninstall Failed dialog box opens.

4. Read the message in the box, and then click OK if you want to uninstall the product.

The Interactive Uninstall dialog box opens.

5. Follow the instructions in the subsequent dialog boxes until uninstallation is complete.

Once the uninstallation is complete, you can reinstall the product software using the product installer. See Chapter 2 for product installation instructions.

What Can I Do If the productregistry File Is Corrupted?

If you attempted to fix the failed installation or uninstallation by using the steps in How Do I Identify and Fix a Failed Installation? or How Do I Fix a Failed Uninstallation?, and you are still having problems, you should delete the corrupted productregistry file from your system. The productregistry file is typically corrupted if you attempt to install or uninstall the software using the pkgadd command or pkgrm command.

1. Become a superuser (root) by typing:

% su
Password: root-password

2. Go to the productregistry file by typing the following command at the prompt:

% cd /var/sadm/install

3. Remove the productregistry file by typing:

# rm productregistry

4. Exit from superuser privileges by typing:

# exit

Once you have removed the productregistry file, you can reinstall the product software using the product installer. See Chapter 2 for product installation instructions.



Note - Deleting the productregistry file removes only the entries for the Forte Developer 7 software. Registry entries for the Solaris operating environment and other products are not affected.




Log Files and Serial Number Files

When you install the Forte Developer 7 software, log files that contain a record of the installation are automatically generated.

How Can I View the Installation Log Files?

To troubleshoot installation problems by viewing the log files, inspect the files at /var/sadm/install/logs.

How Do I Find the Installed Serial Number?

Look at the product log files to locate the serial number. You need the serial number to register the product. You can find the serial number in two ways.

Using -xlicinfo To Find the Serial Number

You can view the contents of the serial.dat file by typing:

% /install-directory/SUNWspro/bin/cc -xlicinfo

Using snit To Find the Serial Number

You can use the snit command to display the serial number in the default license file by typing:

% snit -d

For more information, see the snit(1) man page. If snit is not recognized as a command, set your PATH environment variable, as described in Setting Up Access to the Developer Tools and Man Pages.

What Can I Do If I Lose My Serial Number?

If you lose your serial number and cannot view the contents of the serial.dat file or display your serial number with the snit command, contact customer support at http://wwws.sun.com/software/sundev/suncc/support.html