This section outlines some common problems that can arise when installing WebSphere Business Integration Message Broker. It contains advice for dealing with the problems:
[InstallSheild Silent] Version=v5.00.000 File=LogFile [Application] Name=IBM WebSphere MQ Integrator Version 5.0 Version=2 Company=IBM Lang=0009 [ResponseResult] ResultCode=0
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 |
[date/time] ---> Function: ExitSetup() [date/time] Done: Setup successful - Return Code 0 [date/time] <--- Function: ExitSetup() [date/time] Log stopped. Log Flush = 0.
[07-13 10:22:25] ---> Function: DoMessageBox() [07-13 10:22:25] !!! Silent Install - Message Box Intercept !!! [07-13 10:22:25] Message was: Unable to create target directory [07-13 10:22:25] Severity was: SEVERE, ErrNo was: -30008 [07-13 10:22:25] ABORT was set - ABORT was set [07-13 10:04:51] ---> Function: ExitSetup() [07-13 10:04:51] Done: Setup unsuccessful - Return Code -30008 [07-13 10:04:51] <--- Function: ExitSetup() [07-13 10:04:51] Log stopped.
In this example, the silent installation has failed because the target directory is not valid on this machine. Although a non-silent installation would not fail for this reason (the installation simply does not proceed until the user chooses a valid target directory), a silent installation fails because the response file value is fixed.
Return code | Explanation |
-30000 | User cancelled the install (should never be seen on silent install) |
-30001 | There is another install, or uninstall, running |
-30002 | User ID attempting to perform the install does not have Administrator authority |
-30003 | Install is being attempted on a non-Win32 system |
-30004 | Attempting to install a WebSphere MQ Integrator CSD for the wrong version/release |
-30005 | Attempting to install a CSD when no base product installed |
-30006 | Attempting to install a CSD lower (or equal) to the currently installed CSD |
-30007 | Not enough disk space available to perform install |
-30008 | Unable to create the target directory |
-30009 | The target directory found in the registry does not exist (CSD install) |
-30010 | Failure in creating backup directory (CSD install) |
-30011 | Registry key creation failure |
-30012 | Registry key value setting failure |
-30013 | Failure in creating a program folder entry |
-30014 | InstallShield error |
-30015 | Failure in backing up a file (CSD install) |
-30016 | Invalid operating system detected |
Platform | Location |
AIX | /var/adm/sw |
HP-UX | /var/adm |
Linux (Intel and zSeries) | /var/log |
Solaris | Your home directory (typically / for root) |
Windows | Typically C:\Documents and Settings\<user_login_name> |
The wizard cannot continue because of the following error: could not load wizard specified in /wizard.inf (104)
installp -u mqsi rm -rf /usr/opt/mqsiNow when you try to reinstall WebSphere Business Integration Message Broker the installation fails with a message saying that the product is already installed.
export ODMDIR=/usr/lib/objrepos
odmget vendor | grep GUID | grep -v PGUID | grep mqsiThe console returns a list of entries starting mqsi.
odmdelete -q GUID="mqsi.xx.xxxxx" -o vendor
Related concepts
Types of installation
Related tasks
Installing over a network on Windows
Checking software prerequisites
Installing service on Windows
Dealing with problems
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
au18430_ |