C H A P T E R 15 |
Troubleshooting Problems |
This chapter provides tips for how to troubleshoot problems that you might encounter in the following areas:
This section contains some standard trouble shooting suggestions.
If a problem occurs during installation or uninstallation, check the appropriate log file. Installer and uninstaller log files and reports are found in the following locations:
The following table lists the formats for the log file names. The A version of the log file records completion of the installer. The B version of the log file contains the log messages. Use the Windows utility Notepad to view the log files.
Sun_ONE_Identity_Server_install.Atimestamp Sun_ONE_Identity_Server_install.Btimestamp |
|
The timestamp variable represents the time the log was created. It has the format MMddhhmm, where:
To use the log files for troubleshooting, attempt to isolate the first problem that occurred. Often, the first problem leads to successive problems. Use the following sequence:
1. Review the installation summary file, which provides a high-level description of what was installed and configured.
If a problem occurred, see what component caused the problem. If multiple problems occurred, isolate the first.
2. Review the detailed log files.
a. Look for the first error or warning that occurred and attempt to resolve it. Sometimes resolving one error resolves a number of seemingly unrelated errors that follow.
b. Find the name of the component or package that caused the problem.
The log files can give you clues that determine your next steps, such as these:
3. Examine component product log files.
If a problem occurs starting a component product, examine its log files. Some component products components write log files to the same directory as the installer's log files, including Administration Server, Application Server, Directory Server, Portal Server, and Identity Server. For more information about component product log files, see the appropriate appendix for your platform.
The following host-level issues can cause installation problems.
If you are troubleshooting problems starting up component products, check that the component processes are running and perform the validation procedures in the following chapters (as seems appropriate to the problem you are debugging):
If you are installing from a DVD or CD-ROM, is the media dirty? Dirty discs can result in installation problems due to read errors.
If you are installing a component that relies on Directory Server, one of the following could cause an issue:
The interactive modes of the installer check for Directory Server connectivity during installation, but silent mode does not do so. If you perform a silent installation when Directory Server is not available, the following could occur:
During installation you choose a user name and password. The installer uses the name and password to configure the server component products. This user name and password are used for Application Server, Directory Server and Web Server. Identity Server and Portal Server use a different user name and password. To access the Identity Server Admininstrative Console, type the user name amadmin. The password value is the one you used during installation. Review the Summary_Report.timestamp to verify that you are using the correct login information for each server process.
This section describes some common error conditions you might encounter and suggested solutions for resolving the problems.
1. Trying to reinstall Java Studio Enterprise after uninstalling the software results in the following message from the installer:
Corrupt Serial Number: Installation Cannot Proceed <html><body> A serial number that was installed on the machine appears to have been corrupted. |
Reason. Certain files were not uninstalled properly during a previous uninstall session. You should not see this message unless you have repeatedly installed and uninstalled the software.
Solution. Be sure to remove the following files if they are not removed by the uninstaller:
The Java Studio Enterprise servers have specific dependencies and need to be started in the proper startup sequence. Refer to Chapter 14 for more information.
If the uninstaller stops running before all the product files are deleted, some files, directories, and other system entries may not be properly uninstalled. It is also possible for the installation, configuration, or uninstallation of a component product to fail in such a way that subsequent attempts to uninstall or install fail.
You can identify a failed uninstallation in the following ways:
If you have a failed uninstallation you might encounter problems if you try to reinstall the same or different versions of the software or if you try to install a stand-alone version of Java Studio Enterprise component products.
If you used an uninstallation method other than the provided uninstaller wizard, you might be left with an incomplete or corrupted uninstallation. The following sections describe what to do to fix your system if you determine that you have an incomplete uninstallation.
1. Be sure you are logged in as a user with administrator privileges.
2. Locate the Java Studio Enterprise uninstaller executable, uninstall.bat.
It is found in the java-studio-install-dir. The default installation directory is%SystemDrive%\Sun\jstudio.If this executable is not present, continue to Step 4.
3. Run the uninstaller and continue to Step 4.
4. Verify that all servers are stopped.
Stop the servers using the Start Menu or the command line. To verify, use the following steps:
a. Choose Start > Settings > Control Panel.
The Control Panel dialog box is displayed.
b. Double-click on Administrative Tools.
The Administrative Tools dialog is displayed.
d. Scroll down the list of Services until you see the entries for Sun ONE servers.
The uninstaller may have removed some of the entries. If you see entries for Sun ONE servers that were installed using this installer, then verify they are stopped.
5. Remove the Java Studio Enterprise entries from the productregistry file located at %SystemRoot%\system32\.
To be safe, backup this file before editing the entries if you have installed other Sun software. The variable, %SystemRoot%, on a Microsoft Windows 2000 system might be C:\WINNT.
6. Using the Windows Registry Editor, delete the following folders and their contents from the Windows Registry.
If you have other Sun software products installed, you should just delete the Java Studio Enterprise entries, not the entire folder. You can verify that the entry was installed by Java Studio Enterprise by examining the registry key attribute ImagePath. The value indicates the installation directory, if it's under java-studio-install-dir, then it was installed by the Java Studio Enterprise installer.:
HKEY_LOCAL_MACHINE>SOFTWARE>Sun Microsystems and HKEY_LOCAL_MACHINE>SOFTWARE>Sun
The Java Studio Enterprise entries are:
7. Using the Windows Registry Editor, delete the Sun ONE server registry keys from the following folder:
HKEY_LOCAL_MACHINE>System>CurrentControlSet>Services
The Java Studio Enterprise entries are the following Eventlog entries:
Also remove the following Java Studio Enterprise Services entries:
8. Remove the Start Menu Program Group named Sun Microsystems > Sun Java Studio Enterprise 6 and its contents (Program Items).
9. Remove the product files from the java-studio-install-dir.
If you have trouble deleting some of these directories, check the Task Manager to see if a java.exe process is running. End the java.exe process and try again to delete the java-studio-install-dir and its subdirectories.
10. (Optional) Reboot the system so that the system comes up with a clean registry.
Verify that all Java Studio Enterprise services were removed.
a. Open the Control Panel dialog.
b. Double-click Administrative Tools.
The Administrative Tools dialog is displayed.
The Services dialog is displayed.
d. Scroll down in the list of services to find the Sun Java Studio Enterprise 6 entries.
If you have uninstalled the entire Java Studio Enterprise product, then you should not see any related entries.
Be sure that you have tried running the uninstaller provided with Java Studio Enterprise before using these steps. Normally, the uninstaller completes the uninstallation of the products that you select.
1. Enable client access to the X server.
2. Set the DISPLAY environment variable to display to your local system.
For example, if you use the C shell, type:
4. Verify that all Java Studio Enterprise servers are stopped.
a. If the stopservers script is still available, run the script. For example:
If the stopservers script is not available, you may need to locate the process id for each server and stop it separately. For example:
If the server is running, kill the process. Repeat for each server process. Refer to Appendix D for the Solaris process name corresponding to the servers that you have installed.
5. Verify that all Java Studio Enterprise component product packages were removed.
If you still see packages, see To Manually Remove Packages.
Note - The packages SUNWasvc and SUNWjato do not pose a problem for subsequent install sessions and can be left on your system. |
6. Verify that the uninstaller package was removed.
7. Edit /var/sadm/install/productregistry to remove Java Studio Enterprise entries.
Backup the file before doing manual edits.
8. Remove (if found) /var/sadm/install/.JavaStudio.
9. Remove /var/opt/SUNWappserver7 and /etc/opt/SUNWappserver7 (if you installed Application Server).
10. Remove /var/opt/SUNWam and /etc/opt/SUNWam (if you installed Identity Server).
11. Remove /var/opt/SUNWps and /etc/opt/SUNWps (if you installed Portal Server).
12. Remove java-studio-install-dir/SUNWwbsvr (if you installed Web Server).
13. Remove the remaining files in the java-studio-install-dir.
Note - Remove the program files and directories as the last step in this procedure. |
14. Disable client access to the X server and exit from superuser privileges.
TABLE 15-2 lists the packages installed during Java Studio Enterprise Typical Installation. Use this list as a reference to be sure you removed all of the packages. It is recommended that you only remove these packages manually if the uninstaller wizard failed to remove them. Remove the packages in the order listed in this table using the procedure To Manually Remove Packages.
Java Studio Enterprise component products are listed in the table for reference only and the Sun ONE names are used for correspondence to the software packages. Refer to Product Names for a list of new and old product names.
Sun ONE Administration Server (installed to support Sun ONE Directory Server) |
|
Sun ONE Identity Server Policy Agent for Sun ONE Application Server 7 |
|
1. (Directory Server) If you need to manually remove the packages for Directory Server, follow these steps first:
a. Start the Directory Server instance. For example:
b. Unconfigure Directory Server.
c. Unconfigure Directory Server Administration Console.
2. Remove any Java Studio Enterprise component product packages that have not been removed using the pkgrm command.
Do this carefully and in the order described in TABLE 15-2. Failure to remove the packages in this order may result in unexpected problems due to package dependencies. If you are uncertain how to do this, contact your system administrator.
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.