WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resolving problems when installing
Work through the advice provided to help you to deal with problems that can arise when the product is installed.
The following list describes typical problems when installing, with a corresponding solution or
workaround:
Note: When dealing with the Broker component, the installation log files are
only available after you have exited the installer.
- Broker component:
- Dealing with problems during installation
- Installation process is interrupted
- Installation process is interrupted in console mode
- java.lang.UnsatisfiedLinkError
- RPM query fails
- Display problems
- Insufficient temporary space
- Firewall software reports attempted internet access from an unexpected program
- WebSphere® Message Broker Toolkit:
- WebSphere Message Broker Explorer:
- Installation Manager:
- WebSphere Message Broker Launchpad:
Dealing with problems during installation
Broker component on all operating systems:
Installation process is interrupted
Broker component on all operating systems:
- Scenario: You are installing the Broker component but the process is interrupted before completion.
- Explanation: The process might be interrupted because of a problem, such as a power failure.
- Solution: Delete the install_dir and all its contents before you restart the program.
Installation process is interrupted in console mode
Broker component on Linux:
java.lang.UnsatisfiedLinkError
Broker component on Linux:
- Scenario: You are using the Broker component graphical interface to install on Linux but the interface does not work correctly.
- Explanation: The additional packages that are required to complete the installation are not installed.
- Solution: You must install additional packages for the interface to work correctly. For more information about the required additional packages, see Operating system requirements.
RPM query fails
Broker component on Linux:
Display problems
Broker component on Linux
and UNIX:
Insufficient temporary space
Broker component on Linux
and UNIX:
Firewall software reports attempted internet access from an unexpected program
Broker component on Windows 32-bit
and Windows 64-bit:
WebSphere MQ service fails to install in a Windows domain environment
- Scenario: During installation of the WebSphere MQ
component, you get the following error:
WebSphere MQ configuration problem WebSphere MQ is not correctly configured for Windows domain users. An unexpected error has occurred while validating the security credentials of user 'US\ousdpdghiugan'. Ensure that the network is operational, and that all required domain controllers are available.
- Explanation: You must have a Windows domain account enabled to run WebSphere MQ as a service.
- Solution: To give the domain user (that you obtained from your domain
administrator) the right to run as a service, carry out the following
procedure:
- Click . Type the command secpol.msc and click OK.
- Open . In the list of policies, right-click .
- Click Add User or Group.... Type the name of the user that you obtained from your domain administrator, and click Check Names.
- If you are prompted by a Windows Security window, type the user name and password of an account user or administrator with sufficient authority, and click . Close the Local Security Policy window.
Note: On Windows 7, Windows 8, Windows Server 2008 and Windows Server 2012, the User Account Control (UAC) is enabled by default.The UAC feature restricts the actions users can perform on certain operating system facilities, even if they are members of the Administrators group. You must take appropriate steps to overcome this restriction.
Dealing with problems during installation
WebSphere Message Broker Toolkit on all operating systems:
Dealing with problems during installation
WebSphere Message Broker Explorer on all operating systems:
Installation Manager hangs
Installation Manager on Linux on x86 and Windows:
- Scenario: You click Next in the Installation Manager when it first opens and the Installation Manager hangs.
- Solution: Close the window and reopen it.
Installation Manager does not show the WebSphere Message Broker Toolkit components
Installation Manager on Linux on x86 and Windows:
- Scenario: You are installing the WebSphere Message Broker Toolkit but the initial Install Packages page that is displayed by the Installation Manager does not show the WebSphere Message Broker Toolkit components.
- Explanation: The location of the update repository has not been set correctly.
- Solution: Select Add Preferences. Enter the web address or directory where the installation packages are stored or click Browse to search for the correct location. Click OK. The packages are listed in the Install Packages page. and click
WebSphere Message Broker Launchpad return code indicates that an installation has failed
WebSphere Message
Broker Launchpad on Windows: