Sun ONE logo      Previous      Contents      Index      Next     

Sun ONE Application Server 7 Installation Guide

Chapter 8
Troubleshooting

This chapter describes how to solve common problems that might occur during installation of the Sun™ Open Net Environment (Sun ONE) Application Server 7 software.

The following topics are addressed here:

About Logs

The following Sun ONE Application Server logs can be useful for troubleshooting problems you may have with installation:

Forgotten User Name or Password

If you do not remember the administrative user name that was supplied during installation, try these solutions in this order:

  1. Enter the user name admin. This is the default user name specified in the server configuration dialog during installation.
  2. If this doesn’t work, look in the following file:

    3. domain_config_dir/domain1/admin-server/config/admpw

    This file contains the administrator's user name followed by the encrypted form of the administrative user's password. Seeing the user name may jog your memory.

  3. If this doesn’t work, delete the administrative domain and recreate it with a new password.
  4. As a last resort, uninstall and reinstall the Sun ONE Application Server.

Forgotten Admin Server Port Number

If you do not remember the HTTP server port number of the Admin Server, you can inspect the Admin Server's configuration file to determine the HTTP server port number:

  1. Navigate to domain_config_dir/domain1/admin-server/config/ and open the server.xml file in a text editor.
  2. Look for the following element:

    3. http-listener id="http-listener-1" address="0.0.0.0" port="4848"...

    In this case, port 4848 is the HTTP port number in use.

Connection Refused for Administration Interface

If the connection was refused when attempting to invoke the graphical Administration interface, it is likely that the Admin Server is not running. The Admin Server log file may be helpful in determining the reason the Admin Server is not running.

To start the Admin Server, use the command-line instructions in "Starting and Stopping the Server".

Server Won’t Start: CGI Error Occurs

If the Sun ONE Application Server won’t start, you may receive the following error:

The system may require additional resources. Possible solutions are described in the following sections:

Set Limits on File Descriptions

You can use the ulimit command to determine the number of available file descriptors or set limits on the system’s available file descriptors. The ulimit command displays the limits for the current shell and its descendants.

For sh shell, the ulimit -a command lists all the current resource limits. The ulimit -n command lists the maximum file descriptors plus 1.

Change Kernel Parameters

On Solaris, increase the system resources by modifying the /etc/system file to include the following entries:

The system will require a reboot for the new kernel parameters to take effect.

After you have set the shell resources, the Sun ONE Application Server should start.

Uninstallation Failure Cleanup

If an uninstallation fails, you may need to clean up some leftover files or processes before attempting a new installation.

On UNIX

If an uninstallation fails, you may need to clean up some leftover files or processes before attempting a new installation.

  1. Log in as root.
  2. Navigate to your installation directory and check the content of the /var/sadm/install/productregistry file for installed packages, that is, files having the SUNW string. For example:

    3. cat /var/sadm/install/productregistry | grep SUNW

  3. Run pkgrm for the SUNW packages that were found in the product registry file. For example:

    4. pkgrm SUNWasaco

  4. Remove the following files, if they are present:

    5. /tmp/setupSDKNative

    /tmp/SolarisNativeToolkit_3.0_1

  5. After the packages have been removed, manually remove the Sun ONE Application Server-specific entries from the product registry file itself.

    6. rm /var/sadm/install/productregistry

  6. At the command line, kill all appservd processes that may be running by typing the following:

    7. ps -ef | grep appservd

  7. Remove all remaining files under the Sun ONE Application Server installation directories.
  8. If present, remove the following log file:

    9. /var/sadm/install/logs/Sun_ONE_Application_Server_install.log

    This is necessary because every iteration of installation appends the log information to this file if it exists.

On Microsoft Windows

  1. From the Microsoft Windows Task Manager, stop the WindowsNativeToolkit processes, and remove the corresponding files.
  2. Use the wincleanup utility to remove appserv70-admin, server1, and any other related services.

    3. Note

    If the wincleanup utility is not on your Microsoft Windows machine, you will need to download it. See the Sun ONE KnowledgeBase for more information:
    http://sunsolve.sun.com/pub-cgi/show.pl?target=home

    Run wincleanup using the following syntax:

    wincleanup service_name

    where service_name is the name of your instance server as it is displayed in brackets in the Microsoft Windows Control Panel, on the Services screen. For example, the Services screen might display the following under Name:

    Sun ONE Application Server 7 (server1)

    In this case, the service name is server1.

    For the Admin Server, use admin-server as a service name.

    If no service name is provided, all services associated with the Sun ONE Application Server product will be deleted.

  3. Open the Microsoft Windows registry editor by clicking the Microsoft Windows Start button, choosing Run, and typing regedit in the text box.
  4. Remove the following registry folder and its content:

    5. HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\Application Server

  5. Exit the registry editor.
  6. From Microsoft Windows Explorer, remove the product registry file (system_drive\WinNT\system32\productregistry), or only remove the appserver entries contained in it.
  7. From Microsoft Windows Explorer, delete the product files from the Sun ONE Application Server installation directory.
  8. Reboot the system.

For Microsoft Windows—SNMP Subagent Install Fails

You must install the Microsoft Windows SNMP service before you install the Sun ONE Application Server software. If you receive an error message indicating that installation of the SNMP subagent failed, the Microsoft Windows SNMP service does not exist on your machine and the registration of the associated .dll file failed.

  1. Uninstall the Sun ONE Application Server software.
  2. Install the Microsoft Windows SNMP service.
  3. Reinstall the Sun ONE Application Server software.

Unless otherwise indicated in the installation log, the rest of the product installation is unaffected by failed installation of the SNMP subagent.

For Microsoft Windows—Command Window with Startup Message Does Not Appear

Because some Windows 2000 environments do not properly include the Microsoft Windows net command in the environment, ensure that your system’s environment has access to this command. Refer to "Setting the net Command" for guidelines on resolving this issue.



Previous      Contents      Index      Next     

Copyright 2003 Sun Microsystems, Inc. All rights reserved.