Follow these steps if you are unable to complete the installation or if you get a “failed” installation status for Portal Server.
Consult the following troubleshooting information:
Sun Java System Portal Server 2005Q4 :Chapter 9, Troubleshooting, in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX
Sun Java System Portal Server 2005Q1:Chapter 13, “Troubleshooting,” in Sun Java Enterprise System 2005Q1 Installation Guide
Sun Java System Portal Server 2004Q2:Chapter 11, “Troubleshooting,” in Sun Java Enterprise System 2004Q2 Installation Guide
Sun ONE Portal Server: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.
Collect the general system information as explained in To Collect Required Debug Data for Any Portal Server Problem.
Specify if this is a first-time installation or a Hot Fix installation on a pre-existing Sun ONE Portal Server instance.
Get the installation logs.
On Solaris OS systems and Sun ONE Portal Server (Portal Server 6.0 and 6.1) systems, get the following logs:
/var/sadm/install/logs/pssetup.install.pid/*
On Windows systems, if you chose the Config Later option during the installation, provide the following log files:
server-root\instance_dir\portal\config\logs\*
Get the install error messages.
/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).
/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).
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.