To Collect Debug Data on Messaging Server Installation Problems

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

1. Consult the following troubleshooting information:

   • Messaging Server 6 2005Q4:Chapter 9, Troubleshooting, in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

   • Messaging Server 6 2005Q1:Chapter 13, “Troubleshooting,” in Sun Java Enterprise System 2005Q1 Installation Guide

   • Messaging Server 6 2004Q2:Chapter 11, “Troubleshooting,” in Sun Java Enterprise System 2004Q2 Installation Guide

   • Messaging Server 6 2003Q4:Chapter 9, “Troubleshooting Installation Problems,” in Sun Java Enterprise System 2003Q4 Installation Guide

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

2. Collect the general system information as explained in To Collect Required Debug Data for Any Messaging Server Problem.

3. Specify if this is a first-time installation or a Hot Fix installation on a pre-existing Messaging Server instance.

4. Get the installation logs.

   • Sun Java System Messaging Server (Messaging Server 6):

     Messaging Server 6 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 OS

     /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 Messaging Server (Messaging Server 5): Rerun the installation with the following command and save the resultant file.

     Solaris OS

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

     HP-UX

     tusc -v -feaIT -rall -wall -o /tmp/install-messaging.tusc ./setup

     Linux

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

     Windows

     Use Debug View: http://www.sysinternals.com/Utilities/DebugView.html