To Collect Debug Data for Application Server Installation Problems

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

1. Gather the general system information, as explained in To Collect Required Debug Data for Any Application Server Problem.

2. Specify what kind of installation you have on your server:

   • Package-based or file-based

   • First-time (clean) or upgrade

3. Gather the installation logs.

   • Application Server 9.1

     Solaris

     /var/sadm/install/logs

     The log file names start with Install_Application_Server_*datetime and Sun_Java_System_Application_Server_*datetime, where date and time correspond to the failing installing (for example, 12161532).

     HP-UX and Llinux

     /var/sadm/install/logs

     The log file names start with Install_Application_Server_*datetime and Sun_Java_System_Application_Server_*datetime, where date and time correspond to the failing installing (for example, 12161532).

     Windows

     C:\DocumentsandSettings\current-user\LocalSettings\Temp

     The 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.

   • Application Server 8.1 2005Q1

     Solaris

     truss -ealf -rall -wall -vall -o /tmp/install-appserver.truss ./sjsas_ee-8_1_02_2005Q2-solaris-sparc.bin

     HP-UX

     tusc -v -fealT -rall -wall -o /tmp/install-appserver.tusc ./sjsas_ee-8_1_02_2005Q2-hpux.bin

     Linux

     strace -fv -o /tmp/install-appserver.strace ./sjsas_ee-8_1_02_2005Q2-linux.bin

     Windows

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