Problems when installing

This section outlines some common problems that can arise when installing WebSphere Business Integration Message Broker. It contains advice for dealing with the following problems:

Return codes from a silent installation

To verify that a silent installation is successful, view the log file specified in -f2y in the setup command, and check that ResultCode=0.
An example log for a successful InstallShield installation is shown below:
[InstallSheild Silent]
Version=v5.00.000
File=LogFile
[Application]
Name=IBM WebSphere
Business Integration Message Broker Version 5.0
Version=2
Company=IBM
Lang=0009
[ResponseResult]
ResultCode=0
Non-zero result code values are shown in the following table:
Result code Explanation
-1 General error
-2 Invalid mode
-3 Required data not found in the setup.iss file
-4 Not enough memory available
-5 File does not exist
-6 Cannot write to the response file
-7 Unable to write to the log file
-8 Invalid path to the InstallShield Silent response file
-9 Not a valid list type (string or number)
-10 Data type is invalid
-11 Unknown error during setup
-12 Dialog boxes are out of order
-51 Cannot create the specified folder
-52 Cannot access the specified file or folder
-53 Invalid option selected

The result code 0 (zero) does not confirm a successful installation. You should also check:

The silent installer fails but returns a return code of 0

You get a wizard.inf error when trying to install over a network

On Solaris, a local installation fails with a "class definition not found" error

You cannot reinstall after using the installp -u command

Now you should be able to reinstall WebSphere Business Integration Message Broker.
Start of change

IBM Agent Controller for HP-UX does not start

Related concepts
Types of installation
End of change