WebSphere Application Server Installation Problem Determination
WebSphere Application Server Installation Problem Determination
WebSphere Application Server Installation Problem Determination
Installation on i5/OS
You can install on i5/OS in one of the following ways:
Install locally on i5/OS (silent installation). This type of installation uses a
response file.
Remote installation from a Windows machine using the launchpad and
installation wizards. With this type of installation, you enter your responses
using a GUI interface.
Enable JavaScript
Ensure that JavaScript is enabled in the browser options or preferences. For
example:
In Mozilla for AIX, select Edit Preferences Advanced Scripts &
Plugins - Enable JavaScript for: Navigator, Allow Scripts to: Select all
options.
In Internet Explorer, select Tools Internet Options Security
Internet Custom Level Scripting Active scripting. Select Enable.
In Mozilla Firefox, select Tools Options Content. Select Enable
JavaScript and click Advanced. Select all options.
Collect diagnostics
Collect the installation log as described in Installation log on page 43.
Analyze diagnostics
The installation log includes messages with details of the installation process and
can contain messages that indicate a problem.
Installation fails
Installation errors can have different underlying causes. For example:
This activity helps you to identify the root cause of your installation error and how
to resolve it.
Non-root installation
You can now install WebSphere Application Server V6.1 on distributed systems
using a non-root user ID. You can use this feature with both silent and interactive
mode for full product installations and removals. This type of installation has the
following limitations that can be interpreted as errors:
Product cannot be registered using the native operating system mechanisms
Port conflicts cannot be detected against other users' installations
Ports must use values greater than 1024
Uninstallation and update installation can only be performed by original user,
group member or root
Windows services will not be created during installation
10
Identify symptoms
When using the installation wizard, some errors are caught and displayed before
the installation begins. Messages that you would normally see in the installation
wizard are logged to the installation log when you are doing a silent installation.
Collect diagnostics
To collect diagnostics, collect the installation log as described in Installation log
on page 43.
11
12
If you have this type of error, it is important to note that the installation was
successful and that you do not need to repeat it. You can create the profile
independently using the profile management tool or the manageprofiles
command.
Where to go from here: If your installation was successful but the profile
creation failed, go to Profile creation fails on page 18.
13
Where to go from here: If you found messages that we do not list here, go to
The next step on page 46.
14
i5/OS
Some of the more common reasons that the prerequisite check can fail on i5/OS
include:
JDK 1.5 is not installed
The group PTF for Java not applied
For V5R3: SF99269
For V5R4: SF99291
You can download these products from Fixcentral at:
http://www-912.ibm.com/eserver/support/fixes/fixcentral/main/iseries/
You can find a list of fixes on the installation CD:
cd_root/WAS/lib/V5R3PTFs and cd_root/WAS/lib/V5R4PTFs
15
You can find a complete list of i5/OS prerequisites in the topic iSeries
prerequisites, which is available at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/
com.ibm.websphere.base.iseries.doc/info/iseries/ae/cins_is_prqsvr.html
Distributed
For information about the current prerequisites, see WebSphere Application
Server detailed system requirements, which is available at:
http://www-306.ibm.com/software/webservers/appserv/doc/latest/prereq.html
For information about preparing your system for installation, see Preparing the
operating system for product installation, which is available at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.web
sphere.nd.doc/info/ae/ae/tins_prepare.html
This URL is for the Network Deployment package. If you are installing a different
package, search the Information Center for the page name, tins_prepare.html,
and select the topic that is appropriate for your package.
You can find information about installing on i5/OS using a response file in
Installing WebSphere Application Server from your iSeries server, which is
available at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/
com.ibm.websphere.base.iseries.doc/info/iseries/ae/tins_is_instloc.html
You can find information about customizing the response file for distributed
systems in responsefile.nd.txt, which is available at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.web
sphere.nd.doc/info/ae/ae/rins_responsefile_nd61.html
The following sections describe some of the problems that you might see.
16
17
18
This activity covers problems that occur during the profile creation process and
federation of custom nodes. If your problem occurs after profile creation, for
example, the new application server or deployment manager will not start, see
Installation Verification Test fails on page 35.
Creating profiles
If you are installing the base WebSphere Application Server or Express package,
an application server profile is created automatically. If you are installing the
Network Deployment package, you are given the option to create a profile.
Profiles are created using the manageprofiles command. During installation, this
command is invoked without your knowledge. To create a profile after
installation, you can use the GUI interface to this command (profile management
tool), or you can invoke the command directly.
Profile types
The types of profiles that are available to you depend upon the WebSphere
Application Server package that you have installed:
Application server profile: An application server profile defines one
application server called server1. The default applications are installed.
Deployment manager profile: The deployment manager profile creates the
deployment manager process (dmgr). The deployment manager provides
centralized administration of multiple application server nodes and custom
nodes as a single cell. The deployment manager provides administration for
basic clustering and caching support, including failover support and workload
balancing.
Custom profile: A custom profile defines an empty node that you must
federate to a cell. Federation is done using the addNode command. When
federated, you can use the administration tools to customize the node by
creating servers and clusters. The node does not include a default application
server or default applications.
Cell profile: You can use a cell profile to create a deployment manager, a
federated node, and an application server on that node on a single system. It
creates two profiles, one for the deployment manager and one for the node
and application server.
For Base and Express installations, the application server profile is the only
profile allowed.
19
Identify symptoms
If you are using the installation wizard, the profile management tool, or the
manageprofiles command, error indications are often displayed directly to you. If
you are using a wizard, input is validated and error messages display in the
window where an incorrect parameter is entered. Other messages are displayed
in the Results panel. In the case of the manageprofiles command, error
messages display in the command window. It is important that you make a note
of any of these messages for use in diagnosing the problem.
Typical examples of the types of error messages that you might see include:
Profile creation failed.
Custom profile errors when connecting to the deployment manager:
Unable to connect to the deployment manager using the host name
and port
Unable to connect to the deployment manager using the host name
and port using the specified user name and password.
Authentication failed for deployment manager connection.
If you see any of these messages, go directly to Custom profile federation
error on page 29.
Activity was detected on these ports. (And the port listed is numbered
less than 1024.)
If you have this message, go directly to Invalid ports selected on page 33.
20
Collect diagnostics
The next step in the diagnostic process is to collect the logs that are produced
during installation and profile creation.
The following logs can help you to determine whether the profile was created,
and if it was not, at what stage the process failed:
Profile management tool log
This log is only required if you are using the profile management tool but have
not captured the error messages displayed. For information about collecting
this log, see Profile management tool log on page 45
Profile creation log
For instructions on collecting this log, see Profile creation log on page 44
Installation log
For information about collecting this log, see Installation log on page 43
addNode.log
This log is only required if you are creating a custom profiles and have
selected the option to federate the node to the cell. For information about
collecting this log, see addNode command log on page 45.
(i5/OS) SystemOut JVM log
This log is only required if you are installing to an i5/OS system. For
information about collecting this log, see JVM logs on page 45.
Analyze diagnostics
The next step is to examine each log for messages that indicate the state of the
profile creation and possible errors.
<level>WARNING</level>
<level>SEVERE</level>
<message>Setting ERROR message =
CPWKI0314E
ADMCxxxxE messages
21
Validation errors
The profile management tool validates the input and logs any errors both to the
wizard console and to the profile management tool log.
Example 2 shows the error that is generated when a profile name is specified
that already exists or when the directory for the profile exists.
Example 2 Validation error in the profile management tool log
<record>
<date>2007-03-08T15:21:57</date>
<millis>1173385317140</millis>
<sequence>1151</sequence>
<logger>com.ibm.ws.profile.validators.DirectoryValidator</logger>
<level>SEVERE</level>
<class>com.ibm.ws.profile.validators.DirectoryValidator</class>
<method>runValidator</method>
<thread>10</thread>
<message>The profile path is not valid.</message>
</record>
When you see errors that indicate a problem with the parameters that are
specified, repeat the profile creation using the profile management tool or the
manageprofiles command and correct the input.
If you see the following message, go directly to Invalid ports selected on
page 33:
Activity was detected on these ports. (And the port listed is
numbered less than 1024.)
22
<level>WARNING</level>
<level>SEVERE</level>
<message>INSTCONFSUCCESS: Success: Profile profile_name now exists
<message> INSTCONFFAILED
<message> INSTCONFPARTIALSUCCESS
<message>text - FAILURE</message>
23
A sample log entry that indicates an error would look similar to that shown in
Example 4.
Example 4 Example of an error entry
<record>
<date>2007-03-08T11:00:35</date>
<millis>1173369635312</millis>
<sequence>14855</sequence>
<logger>com.ibm.ws.profile.cli.WSProfileCLICreateProfileInvoker</logger
>
<level>SEVERE</level>
<class>com.ibm.ws.profile.cli.WSProfileCLICreateProfileInvoker</class>
<method>executeWSProfileAccordingToMode</method>
<thread>10</thread>
<message>INSTCONFFAILED: The profile could not be created. For more
information, consult the
C:\WebSphere\AppServer\logs\manageprofiles\create.log file.</message>
</record>
<record>
<date>2007-02-26T14:36:47</date>
<millis>1172518607687</millis>
<sequence>5651</sequence>
<logger>com.ibm.ws.profile.cli.WSProfileCLICreateProfileInvoker</logger
>
<level>INFO</level>
<class>com.ibm.ws.profile.cli.WSProfileCLICreateProfileInvoker</class>
<method>executeWSProfileAccordingToMode</method>
<thread>10</thread>
<message>INSTCONFSUCCESS: Success: Profile Custom01 now exists.
Please consult
C:\WebSphere\AppServer\profiles\Custom01/logs/AboutThisProfile.txt for
more information about this profile.</message>
</record>
24
<record>
<date>2007-03-13T11:26:33</date>
<millis>1173795993062</millis>
<sequence>38</sequence>
<logger>com.ibm.wsspi.profile.WSProfileException</logger>
<level>WARNING</level>
<class>com.ibm.wsspi.profile.WSProfileException</class>
<method>WSProfileException</method>
<thread>10</thread>
<message>Exception message is: Cannot locate the template: No profile
template exists at path
E:\WebSphere\AppServer\profileTemplates\defaul.</message>
</record>
25
This error also causes the following response in the manageprofiles window:
Cannot locate the template: No profile template exists at path...
If you see this message, go to Template path error on page 28.
26
27
ADFS messages
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.we
bsphere.messages.doc/com.ibm.ws.management.resources.fileservice.html
28
29
Verify that the host of the custom profile node can do a host name lookup on
the deployment manager node.
Verify that the deployment manager system and the new node system have
synchronized date and time.
Recreate the profile, or if the profile was successfully created, federate the
node using the addNode command.
Tip: If you are having trouble finding the cause of the federation error, create
the profile and elect to federate later. Then, after the profile is created, open a
command line and use the addNode command to federate. The errors will be
more visible and retrying the process will be faster.
30
31
32
Deleting profiles
To delete a profile, do the following:
If you are removing a custom profile or application server profile that has
been federated to a cell:
a. Stop the application servers on the node.
b. Remove the node from the cell using the administrative console or the
removeNode command. Removing a node does not delete it, but restores it
to its pre-federated configuration that was saved as part of the federation
process.
c. Delete the profile using manageprofiles -delete.
d. Use the manageprofiles -validateAndUpdateRegistry command to clean
the profile registry.
e. Delete the profile_home directory.
If you are removing an application server profile that has not been federated
to a cell:
a. Stop the application server.
b. Delete the profile using manageprofiles -delete.
33
34
Note: If there are problems during the delete, you can delete the profile
manually. For information, see Deleting a profile, which is available at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.
websphere.nd.doc/info/ae/ae/tpro_removeprofile.html
i5/OS
app_server_root/bin/ivt server1 default
To run this script, your user profile must have *ALLOBJ authority.
The IVT does the following:
Displays information about the profile
Starts the server (application or deployment manager depending on the
profile)
Scans the logs for warnings and errors related to the start of the server and
displays any of these messages it finds
35
Identify symptoms
When you run the IVT from the First Steps console, messages indicating the
status of the tests and error messages display directly in the console. When
running the command, the messages display in the command window. The
messages are also logged to the ivtClient and startServer logs.
Symptoms of an IVT failure include:
IVTL0075I: The Installation Verification Tool verification failed.
ADMUxxxxE messages
WSVRxxxxE messages.
Warnings might or might not indicate an error. They are most often useful when
they closely precede an error. Example 11 illustrates what displays when starting
the deployment manager in a successful IVT test.
Example 11 Warnings shown in a successful IVT
Port conflicts
The most common cause for problems in the IVT are port conflicts. Processes
that are defined by profiles use a set of IP port numbers. For the process
(application server, node, or deployment manager) start, these ports must not be
in use by other processes.
If you see the Conflict detected on port xxxx message in a log or in the ivt
results, go to Port conflicts on page 40.
36
Collect diagnostics
Collect the following information:
Profile creation log (see Profile creation log on page 44)
IVT log (see IVT log on page 44)
Start server log (see Start server log on page 44)
SystemOut and SystemErr JVM logs (see JVM logs on page 45)
Analyze diagnostics
Note that many error messages are included in multiple logs. Scan these logs in
the order that we list here and when you find an indicator of the problem, use the
messages to go to the root cause explanation, or to form a search of online
support resources.
<level>WARNING</level>
<level>SEVERE</level>
<message> INSTCONFFAILED
<message> INSTCONFPARTIALSUCCESS
<message>text - FAILURE</message>
37
ADMUxxxxE messages
Review the text and user response information for these messages for possible
solutions. You can find the message text and user response information at
ADMU messages, which is available at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.web
sphere.messages.doc/com.ibm.ws.management.resources.nodeutils.html
38
Analyze startServer.log
Look for errors that related to the attempt to start the server. Scanning from the
top, look for:
ADMUxxxxE, ADMUxxxxW
Any other messages ending with E (errors) or W (warnings).
Warning messages by themselves do not often indicate a problem. However,
warning message in the presence of error messages should be noted.
Review the text and user response information for these messages for possible
solutions. You can find the text and user response information for ADMU
messages at ADMU messages, which is available at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.web
sphere.messages.doc/com.ibm.ws.management.resources.nodeutils.html
39
Port conflicts
The port might already be in use. If you have port conflicts, follow these steps:
1. Look for another running server process that uses the same ports.
You can find the ports in use by WebSphere processes in
profile_home/properties/portdef.props.
2. Use the netstat command to see if the port is in use:
UNIX / Linux: netstat -an | grep LISTEN
Windows: netstat -an. Look for ports in LISTENING state.
40
41
Identify symptoms
Because the update is run in batch, a failure can only be seen by looking in the
logs. The most likely symptom of a failure in the update process is that an error
you applied a fix to correct is still occurring.
Collect diagnostics
Collect all the files in the following location:
app_server_root/logs/update/6.1.0-WS-WAS-i5osPPC-FP000000x.install
Analyze diagnostics
Scan each log for indications of an error. Search for the text error. Error
conditions addressed in this paper are:
If you find error messages not listed here or you see no messages that indicate
the problem, go to The next step on page 46.
42
Authority error
This error is issued when the user who initiated the job does not have enough
authority to run the update script. The user initiating the update script must have
*ALLOBJ authority.
Collecting logs
This section provides more information about where to find the diagnostic data
for installation problems.
Installation log
You can find the installation log at the following location:
i5/OS
When the installation is performed locally on i5/OS (silent):
app_server_root/V61/install_ver/logs/install/log.txt
where install_ver = Base, ND, Express
When the installation is remote to i5/OS from a Windows system:
user.home\Local Settings\temp\niflogs
where user.home is generally \Documents and Settings\userid (or
administrator)
43
Distributed platforms
app_server_root/logs/install/log.txt
If the installer fails at a very early stage, this log file might not be created or it
might exist in the system temporary area, %TEMP%\log.txt in Windows or
/tmp/log.txt in UNIX.
Tip: If the installation wizard will not start and there is no installation log, try
repeating the installation using a silent install with the -log parameter to
create the log (for example, Windows):
install -options response_file -silent -log # !log_file_name
@ALL
IVT log
Messages issued during the Installation Verification Test are issued directly to
the console and also logged at Distributed platforms,
profile_root/logs/ivtClient.log.
44
JVM logs
JVM logs, often referred to as SystemOut and SystemErr logs, are created for
every WebSphere Application Server process (application server, cluster
member, node agent, and deployment manager). For WebSphere Application
Server V6.x (distributed and i5/OS), you can find them in the following locations:
The JVM log files are by default named SystemOut.log and SystemErr.log.
The default location for the SystemOut and SystemErr logs is:
profile_root/logs/server_name/SystemOut.log
profile_root/logs/server_name/SystemErr.log:
The location of application server logs is configurable.
a. Select Troubleshooting Logs and Trace in the navigation bar.
b. Click on the server name.
c. Select JVM logs
This page shows location of the log file.
45
Contact IBM
If these steps do not resolve your problem, then gather additional information as
specified in the following MustGather document and raise a problem record
(PMR) with IBM. The following URL contains a list of the MustGather
documentation for installation problems.
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21255887
46
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s) described in this publication at
any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on
the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrates programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the
sample programs are written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to IBM for the purposes of
developing, using, marketing, or distributing application programs conforming to IBM's application
programming interfaces.
Copyright International Business Machines Corporation 2007. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by
GSA ADP Schedule Contract with IBM Corp.
47
Redpaper
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
Redbooks (logo)
iSeries
i5/OS
AIX
IBM
WebSphere
48