test

Sun Java Enterprise System 5 Installation Guide for Microsoft Windows

Chapter 8 Troubleshooting

This chapter provides suggestions for how to resolve Sun Java Enterprise System (Java ES) installation and uninstallation problems.

This chapter includes the following sections:

General Troubleshooting Methods

This section provides general guidelines for finding the source of a problem. The following topics are addressed:

Network Connectivity

Java ESinstallation is not supported on a stand-alone machine. You must have a machine connected to a network to install Java ES.

Check Directory Server Connectivity

If you are installing a component that relies on Directory Server, problems can be caused by one of these situations:

In Configure Manually After Installation mode, you need to ensure that the Directory Server is running before configuring the products that depend on Directory Server.

Check Postinstallation Configuration

If you are having problems starting components, verify that the procedures outlined in Chapter 5, Completing Postinstallation Configuration were performed correctly.

Check Resources and Settings

The following host-level issues can cause installation problems:

Refer to System Requirements to check if all the requirements have been met before proceeding to installation.

Check the Distribution Media

If you are installing from a DVD, examine the media for dirt or damage. Dirty discs can result in installation problems.

Examine Component Log Files

If a problem occurs when starting a component, examine its log files. Many component log files are listed under Component Troubleshooting Information.

Examine the Installation Log Files

If a problem occurs during installation or uninstallation, check the appropriate log file in the %TEMP%/SunJavaES.log directory.

%TEMP% is the user-defined TEMP folder on that system.

Examining the uninstaller and installer log files (along with the Java ES configuration log) can help locate the source of problems.

ProcedureTo Examine Installation Log Files

  1. Review the installation summary file, which provides a high-level description of what was installed and configured. This file is located at JavaEs-install-dir\Summary.txt. If a problem occurred, check which component caused the problem. If multiple problems occurred, isolate the first one.

  2. Review the detailed log files.

    1. Look for the first error or warning that occurred and attempt to resolve the error. Sometimes resolving one error resolves a number of seemingly unrelated errors that follow.

    2. Find the name of the component that caused the problem.

    3. Review the configuration logs. The configuration logs are in component installation directories. Refer to Summary.txt to find the exact location of component log files.

    4. Review the installer log file for installation or uninstallation issues. Refer to configuration logs for configuration-related issues.

Remove Files and Directory

To prevent the overwriting of customized files, such as edited configuration files, Java ES 5 components cannot be installed in their respective installation directories that contain files.

If you are reinstalling Java ES 5, check the installation directories to ensure that they are empty. If these directories are not empty, archive the files elsewhere and try the installation again.

Verify Passwords

The installer requires that you enter a number of passwords for components. If you are installing different components on different hosts, make sure that you supply matching passwords on each host.

To resolve password problems, you might need to uninstall and then reinstall. If the uninstallation fails, refer to Installation Fails Due to Remaining Files During Uninstallation.

Verify Component Dependencies

A number of components have installation-time interdependencies. Problems that affect one component can affect other components. To check for interdependencies not met, familiarize yourself with the information in Dependency Check. Then, do the following:

Installation Problems

This section addresses the following problems you might encounter during installation:

Installation Fails Due to Remaining Files During Uninstallation

If uninstallation fails, components that should have been removed might remain on your host system. In such a case, you must manually remove the components before you reinstall Java ES.

ProcedureTo Remove Remaining Files

The following cleanup steps are required before reinstalling the Java ESafter a failed installation or a failed unconfiguration.

  1. Ensure that all the Java ES services are stopped and removed from the Control Panel > Administrative Tools > Services menu.

  2. Delete any previously installed Sun folder. If you are not able to delete the folder, restart the system and then delete the folder.

  3. Check for any remaining service entries. If any service entry is remaining in Services, you need to clean up the registry by removing the entries. Possible entries are listed in the following table.

    Component Name  

    Service Entry  

    Common Agent Container 

    Common Agent Container 2 (#CRC:default) 

    HADB 

    HADB4.4MgmtAgent

    Message Queue 

    MQ3.7UR1_Broker

    Portal Server 

    sra.gateway.srainstance

    sra.netletproxy.srainstance

    sra.rewriterproxy.srainstance

    WebAdminServer 

    https-admserv70

    Web Console 

    Web Console 3.0.2 console  

    Web Proxy Server 

    Sun Java System Socks Server 4.0.4 (server1)

    Sun Java System Web Proxy Server 4.0.4 (proxy-server1)

    Sun Java System Web Proxy Server 4.0.4 Administration Server  

    Web Server 

    Sun Java System Web Server 7.0 (https-hostname.domainname)

    Sun Java System Web Server 7.0 Administration Server 

  4. Clean up the registry.

    Delete HKEY_LOCAL_MACHINE\Software\Sun Microsystems\Entsys5\Installer.

  5. If you perform any of the previous steps, restart the system before you start the installation.

Windows Installer Errors

Installation can fail due to the following Windows installer error.

Silent Installation Fails

If you edited the response file, you might have introduced errors. For example, check the following:

Resolve the problem and regenerate the response file as described in Creating a Response File.

Silent Installation Fails: “Response File Is Incompatible or Corrupted”

If you are using a response file that was created on the same platform on which you are using the response file, the problem might be due to an unknown file corruption error. Try to generate a new response file and reinstall.

For more information, refer to Creating a Response File.

Unexpected External Errors

Possible causes for external errors are the following:

If the failure occurred during the installation or configuration process, you probably have a partial installation. Run the uninstallation program. If the uninstallation program fails, follow the instructions under Installation Fails Due to Remaining Files During Uninstallation.

Component Troubleshooting Information

This section provides various quick tips on component troubleshooting, with references to useful documentation:

Access Manager Troubleshooting Tips

Table 8–1 Access Manager Troubleshooting Tips

Topic 

Details 

Configuration File 

AccessManager-base\Config\AMConfig.properties

Log and Debug Files 

Log file directory: 

AccessManager-base\Logs

Debug file directory: 

AccessManager-base\Debug

Debug Mode 

Refer to the Sun Java System Access Manager Developer’s Guide.

Application Server Troubleshooting Tips

Table 8–2 Application Server Troubleshooting Tips

Topic 

Details 

Log Files 

Log file directory: 

ApplicationServer-base\Setup\

Application Server instance log directory (default location for the initially created instance): 

JaveES-install-dir\appserver\

Message log file name: server.log, for each server instance.

Configuration Files 

Configuration file directory: ApplicationServer-base\Config.

Troubleshooting 

Refer to the Sun Java System Application Server Enterprise Edition Troubleshooting Guide.

Directory Server Troubleshooting Tips

Table 8–3 Directory Server Troubleshooting Tips

Topic 

Details 

Log Files 

Installation log file can be found in tmp folder.

Configuration log files: 

  • DirectoryServer-base.Atimestamp

  • DirectoryServer-base.Btimestamp

For information about managing log files, refer to the Sun Java System Directory Server Administration Guide

Troubleshooting 

Refer to the Sun Java System Directory Server Administration Guide.

HADB Troubleshooting Tips

Table 8–4 HADB Troubleshooting Tips

Topic 

Details 

Log Files 

  • HADB.properties

  • mgt.cfg

Executable Location 

JavaES-install-dir\Hadb\4.4.1-7\lib

Troubleshooting 

Refer to the High Availability Session Store Administrator’s Guide.

Message Queue Troubleshooting Tips

Table 8–5 Message Queue Troubleshooting Tips

Topic  

Details 

Log Files 

Installation Log file: 

MessageQueue-base\var\instances\instance-name\log

Refer to the Sun Java System Message Queue 3.7 UR1 Administration Guide.

Troubleshooting 

For performance problems, refer to Chapter 11, Analyzing and Tuning a Message Service, in Sun Java System Message Queue 3.7 UR1 Administration Guide.

Message Queue troubleshooting is discussed in Chapter 12, Troubleshooting Problems, in Sun Java System Message Queue 3.7 UR1 Administration Guide. and the Message Queue Forum, at: http://swforum.sun.com/jive/forum.jspa?forumID=24.

Additional articles are available in Knowledge Base, at http://developers.sun.com/prodtech/msgqueue/reference/techart/index.html.

Monitoring Console Troubleshooting Tips

Table 8–6 Monitoring Console Troubleshooting Tips

Topic 

Details 

Configuration Files 

For Monitoring Console: 

  • MonitoringConsole-base\WEB-INF\web.xml

For Monitoring Framework: 

  • JavaES-install-dir\share\mfwk\config\mfwk.properties

Log Files 

For Monitoring Console: 

  • JavaES-install-dir\share\webconsole\console\console_config_log

For Monitoring Framework: 

  • JavaES-install-dir\share\mfwk\logs

Troubleshooting 

If you cannot access Monitoring Console, refer to Troubleshooting the Monitoring Console in Sun Java Enterprise System 5 Monitoring Guide. For troubleshooting Monitoring Console, refer Troubleshooting the Monitoring Framework in Sun Java Enterprise System 5 Monitoring Guide.

Portal Server Secure Remote Access Troubleshooting Tips

Table 8–7 Portal Server Secure Remote Access Troubleshooting Tips

Topic 

Details 

Debug Logs 

Portal gateway debug logs are located in the PortalServer-base\debug directory.

Note –

Logs for Portal Server services (such as NetFile) are in AccessManager-base\debug directory when logging is turned on from Access Manager Administration Console.

Portal Server Troubleshooting Tips

Table 8–8 Portal Server Troubleshooting Tips

Topic  

Details 

Log Files and Debug Files 

Portal Server log files are: 

  • psadmin logs: PortalServer-base\data\admin

  • Configuration logsPortalServer-base\data\config

  • Portal Server instance logs: PortalServer-base\data\portals\portal-id\logs\instance-id

Service Registry Troubleshooting Tips

Table 8–9 Service Registry Troubleshooting Tips

Topic 

Details  

Log Files 

Default log file:ServiceRegistry-base\domains\registry\logs\server.log

For more information, refer to the Service Registry 3.1 Administration Guide.

Troubleshooting 

Refer to the Service Registry 3.1 Administration Guide.

Web Proxy Server Troubleshooting Tips

Table 8–10 Web Proxy Server Troubleshooting Tips

Topic 

Details 

Log Files 

Default log files: 

  • JavaES-install-dir\instance-name\config\logs\errors

  • JavaES-install-dir\instance-name\config\logs\access

  • JavaES-install-dir\admin-name\config\logs\errors

  • JavaES-install-dir\admin-name\config\logs\access

For more information, refer Sun Java System Web Proxy Server Administration Guide.

Troubleshooting 

Refer to the Sun Java System Web Proxy Administration Guide.

Web Server Troubleshooting Tips

Table 8–11 Web Server Troubleshooting Tips

Topic  

Details 

Log Files 

The errors log file and the access log file are located in the WebServer-base\WebServer_Install.log directory.

The errors log file lists all the errors that the server has encountered. The access log records information about requests to the server and the responses from the server. For more information, refer to the Sun Java System Web Server 7.0 Administrator’s Guide.

Troubleshooting 

Refer to the Sun Java System Web Server 7.0 Troubleshooting Guide.

Configuration File Directory 

WebServer-base\https-instance-name\config

Additional Troubleshooting Information

The following additional information in this guide is useful for troubleshooting: