To Gather Debug Data on Web Server Installation Problems

Follow these steps if you are unable to complete the installation or if you get a “failed” installation status for Web Server.

1. See the following troubleshooting information:

   • Sun Java Enterprise System 5:

     http://docs.sun.com/app/docs/doc/820-0464

   • Sun Java Enterprise System 2005Q4:

     Chapter 9, Troubleshooting, in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

   • Sun Java Enterprise System 2005Q1:

     http://docs.sun.com/source/819-0056/troubleshooting.html

   • Sun Java Enterprise System 2004Q2:

     http://docs.sun.com/source/817-5760/troubleshooting.html

   • Sun Java Enterprise System 2003Q4:

     http://docs.sun.com/source/816-6874/std-troubleshooting.html

   If the problem persists after using this troubleshooting information, then continue with this procedure to gather the necessary data for the Sun Support Center.

2. Gather the general system information as explained in To Gather General Debug Data for Any Web Server Problem.

3. Specify whether this is a first-time installation or a Hot Fix installation on a pre-existing Web Server.

4. Get the installation logs.

   • Sun Java System Web Server (Web Server 7.0):

     Web Server 7.0 log files mostly reside in the server-root/log directory. However, the initial configuration log files reside in the server-root/install directory, which also contains information on the initial configuration.

     Solaris

     /var/sadm/install/logsThe log file names start with Java_Enterprise_System*_install.Bdatetime, where date and time correspond to the failing installing (for example, B12161532).

     HP-UX and Linux

     /var/opt/sun/install/logsThe log file names start with Java_Enterprise_System*_install.Bdatetime, where date and time correspond to the failing installing (for example, B12161532).

     Windows

     C:\DocumentsandSettings\current-user\LocalSettings\TempThe log file names start with MSI*.log (usually a text file). The asterisk (*) represents a random number in the Temp directory for each MSI based setup.

   • Sun Java System Web Server (Web Server 6.1):

     Web Server 6.1 log files mostly reside in the server-root/log directory. However, the initial configuration log files reside in the server-root/install directory, which also contains information on the initial configuration.

     Solaris

     /var/sadm/install/logsThe log file names start with Java_Enterprise_System*_install.Bdatetime, where date and time correspond to the failing installing (for example, B12161532).

     HP-UX and Linux

     /var/opt/sun/install/logsThe log file names start with Java_Enterprise_System*_install.Bdatetime, where date and time correspond to the failing installing (for example, B12161532).

     Windows

     C:\DocumentsandSettings\current-user\LocalSettings\TempThe log file names start with MSI*.log (usually a text file). The asterisk (*) represents a random number in the Temp directory for each MSI based setup.

   • iPlanet Web Server (Web Server 6.0):

     Rerun the installation with the following command and save the output file.

     Solaris

     truss -ealf -rall -wall -vall -o /tmp/install-web.truss ./setup

     HP-UX

     tusc -v -fealT -rall -wall -o /tmp/install-web.tusc ./setup

     Linux

     strace -fv -o /tmp/install-web.strace ./setup

     Windows

     Use DebugView tool. You can download this tool from http://www.sysinternals.com/Utilities/DebugView.html