IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

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 Integration Bus component, the installation log files are only available after you have exited the installer.

Integration Bus component:
IBM® Integration Toolkit:
- Dealing with problems during installation
IBM Integration Explorer:
- Dealing with problems during installation
Installation Manager:
- Installation Manager hangs
- Installation Manager does not show the IBM Integration Toolkit components
IBM Integration Bus Launchpad:
- IBM Integration Bus Launchpad return code indicates that an installation has failed

Dealing with problems during installation

Integration Bus component on all operating systems:

Scenario: You have problems during the installation of the Integration Bus component.
Solution: Complete the following steps:
1. If you experience problems when installing on z/OS®, see the Program Directory for IBM Integration Bus for z/OS on the IBM Integration Bus Library web page.
2. Refer to the readme file readme.html for any late changes to the installation instructions.
3. If you transferred the installation media to your local or networked filesystem, you might see the following error:
```
The Install executable launcher was unable to locate its 
companion shared library.
```
  Ensure that you have read and execute privileges on all installation directories and files. Also ensure that the length of the path to the installation media is within the limits imposed by your operating system.
4. If installation is successful, the installation wizard returns a return code of zero. If a non-zero return code is returned, check the installation log file for errors and explanations. Problems associated with the installation of the Integration Bus component are recorded in the log file IBM_Integration_Bus_InstallLog.log, which is stored in your installation directory.
  If you accepted the default location during installation, this directory is as follows. The default directory includes the version, release, modification, and fix of the product that you are installing in the format v.r.m.f (version.release.modification.fix):
  Linux
  
  /opt/ibm/mqsi/v.r.m.f
  
  UNIX
  
  /opt/IBM/mqsi/v.r.m.f
  
  Windows 32-bit
  
  C:\Program Files\IBM\MQSI\v.r.m.f
  
  Windows 64-bit
  
  C:\Program Files\IBM\MQSI\v.r.m.f for the 64-bit version of IBM Integration Bus
  
  C:\Program Files (x86)\IBM\MQSI\v.r.m.f for the 32-bit version of IBM Integration Bus
  
  These locations define the default value of install_dir on each platform.
5. If you are still unable to resolve the problem, contact your IBM Support Center.

Installation process is interrupted

Integration Bus component on all operating systems:

Scenario: You are installing the Integration Bus 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

Integration Bus component on Linux:

Scenario: Installation in console mode is interrupted by an InvocationTargetException error, with the following information included in the stack trace:

java.lang.NoClassDefFoundError: sun.awt.X11GraphicsEnvironment (initialization failure)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:176)
	at java.lang.Class.forNameImpl(Native Method)
	at java.lang.Class.forName(Class.java:182)
	at java.awt.GraphicsEnvironment.createGE(GraphicsEnvironment.java:113)
	at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:92)
	at sun.awt.X11FontManager.isHeadless(X11FontManager.java:499)
	at sun.awt.X11FontManager.getFontPath(X11FontManager.java:779)
	at sun.font.SunFontManager.getPlatformFontPath(SunFontManager.java:3300)
	at sun.font.SunFontManager$11.run(SunFontManager.java:3326)
	at java.security.AccessController.doPrivileged(AccessController.java:229)
	at sun.font.SunFontManager.loadFonts(SunFontManager.java:3322)
	at sun.awt.X11FontManager.loadFonts(X11FontManager.java:451)
	at sun.font.SunFontManager.findFont2D(SunFontManager.java:2359)
	at java.awt.Font.getFont2D(Font.java:509)
	at java.awt.Font.getFamily(Font.java:1198)
	at java.awt.Font.getFamily_NoClientCode(Font.java:1172)
	at java.awt.Font.getFamily(Font.java:1164)
	at Flexeraanx.al(Unknown Source)
	...

Explanation: A MIT-MAGIC-COOKIE-1 is present on the system. The installer attempts to connect to a display, but the link to the display is not correctly configured.
Solution:
1. Delete the install_dir directory, and its contents.
2. In the command prompt, run the command unset DISPLAY.
3. Run the installation again in console mode.

java.lang.UnsatisfiedLinkError

Integration Bus component on Linux:

Scenario: You are using the Integration Bus 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

Integration Bus component on Linux:

Scenario: You start a Red Hat package manager (RPM) query after you have installed the product, but nothing is returned. An information message like the following example might have been reported in the installation log file:

(01-Jun-2005 09:02:27), mqsi.Setup,
   com.ibm.wizard.platform.linux.LinuxProductServiceImpl, wrn, 
   The installer could not successfully add the product information 
   into the RPM database. Installation will continue as this is not 
   critical to the installation of the product.

Explanation: It is likely that your system does not have the required RPM support.
Solution: Install the additional RPM build package that is described in Operating system requirements.

Display problems

Integration Bus component on Linux and UNIX:

Scenario: You try to install the Integration Bus component by using the graphical interface and see one of two common errors reported.
Explanation: Both errors typically occur if you log in remotely, or you switch user ID.
Solution: Address the appropriate error with the following corresponding solution:
Can't open display localhost:1.0

Check that the DISPLAY variable is set to the correct value. If you are logged in locally, the typical value is :0.0 or localhost:0.0.

Connection to ":0.0" refused by server
Run the following command, where user is the user ID you are logged in as:
```
xauth merge ~user/.Xauthority
```
If you are unable to correct these errors, contact your systems administrator for further help.

Insufficient temporary space

Integration Bus component on Linux and UNIX:

Scenario: You install the Integration Bus component and the installation program tries to unpack product files into the temporary file space of the local system. On Linux and UNIX systems, the temporary space is typically located in /tmp.
Explanation: If sufficient file space is not available in this directory, the command might fail without reason and return no comment, or might report a lack of file space.
Solution: Set the environment variable IATEMPDIR to the temporary file system to use. For example, enter the following command:
```
export  IATEMPDIR=/largetemp
```
Do not specify a temporary directory that is NFS-mounted from another server; if you do so, the installation might fail because user permission checks made by the installer sometimes report an error that security principals mqm and mqbrkrs do not exist on the local machine.
Or if using SUDO, enter the following command:
```
SUDO env IATEMPDIR=/largetemp ./setupaix
```
For more information about checking how much temporary space is required, see Memory and disk space requirements.

Firewall software reports attempted internet access from an unexpected program

Integration Bus component on Windows 32-bit and Windows 64-bit:

Scenario: During installation of the Integration Bus component, your firewall software reports attempted internet access from an unexpected program. One of the following program name displays:
```
C:\long_generated_hexadecimal_string\setup32.exe
```
```
C:\long_generated_hexadecimal_string\setup64.exe
```
Explanation: Internet access is not required to complete the installation of the Integration Bus component. However, this component also installs an updated Microsoft C runtime library that might attempt internet access during its installation, which might cause firewall software to report a warning.
Solution: This is normal behavior for this component, and installation completes successfully whether you allow access or not.

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:
1. Click Start > Run.... Type the command secpol.msc and click OK.
2. Open Security Settings > Local Policies > User Rights Assignments. In the list of policies, right-click Log on as a service > Properties.
3. Click Add User or Group.... Type the name of the user that you obtained from your domain administrator, and click Check Names.
4. 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 OK > Apply > OK. 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

IBM Integration Toolkit on all operating systems:

Scenario: During installation, you get the following error message:

You cannot update a 64-bit version of Installation Manager to a 32-bit version.

Explanation: A 64 bit version of IBM Installation Manager is already installed. This version is less than v1.6.2, and is not compatible with the 32 bit version that the IBM Integration Toolkit requires.
Solution:
1. Cancel the installation.
2. Launch the existing 64 bit version of IBM Installation Manager.
3. Click File > Preferences and select Updates.
4. Select Search for Installation Manager updates. Click OK.
5. Click Update from the Installation Manager main wizard and click Yes when prompt to upgrade to the latest version.
6. Close the Installation Manager after the update is completed.
7. Restart the toolkit installation.

Scenario: You have problems during the installation of the IBM Integration Toolkit.
Solution: Complete the following steps:
1. Refer to the readme file readme.html for any late changes to the installation instructions.
2. If installation is successful, the installation wizard returns a return code of zero. If a non-zero return code is returned, check the Installation Manager log file for errors and explanations. Problems associated with the installation of the IBM Integration Toolkit are recorded in the Installation Manager log file YYYYMMDD_TIME.xml. Where YYYYMMDD_TIME is the date and time of installation. The Installation Manager log file is stored in the following location:
  Linux
  
  /var/ibm/InstallationManager/logs
  
  Windows
  
  On Windows systems, the directory is created in the following default location, however the actual location might differ on your computer:
  C:\ProgramData\IBM\Installation Manager\logs
3. If you are still unable to resolve the problem, export the Installation Manager related information from Installation Manager > Help menu > Export Data for Problem Analysis, and contact your IBM Support Center with the exported information.

Dealing with problems during installation

IBM Integration Explorer on all operating systems:

Scenario: You have problems during the installation of the IBM Integration Explorer.
Solution: Complete the following steps:
1. See the Program Directory for IBM Integration Bus for z/OS if you experience problems when installing on z/OS.
2. Refer to the readme file readme.html for any late changes to the installation instructions.
3. If installation is successful, the installation wizard returns a return code of zero. If a non-zero return code is returned, check the log file for errors and explanations. Problems associated with the installation of the IBM Integration Explorer are recorded in the log file IBExplorer_install.log, which is stored in the installation directory. The default installation directories are as follows:
  Linux
  
  /opt/IBM/IBExplorer
  
  Windows
  
  C:\Program Files\IBM\IBExplorer

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 IBM Integration Toolkit components

Installation Manager on Linux on x86 and Windows:

Scenario: You are installing the IBM Integration Toolkit but the initial Install Packages page that is displayed by the Installation Manager does not show the IBM Integration Toolkit components.
Explanation: The location of the update repository has not been set correctly.
Solution: Select File > Preferences and click 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.

IBM Integration Bus Launchpad return code indicates that an installation has failed

IBM Integration Bus Launchpad on Windows:

Scenario: You install products by using the IBM Integration Bus Launchpad. The Launchpad waits for a return code from each installation wizard that it initiates, but the return code indicates that an installation has failed. The Launchpad reports the error and refers you to the documentation for the product that has failed.
Explanation: Most installation wizards roll back from the point of the error and return your system to the state it was in before the failed attempt, and you can therefore try again after you have corrected the error. However, in this scenario, the Launchpad has already installed one or more products successfully before the error occurred, so does not roll back these installations. When you restart the Launchpad, the status of installed products reflects successful installations from the previous invocation.
Solution: To resolve the failed installation, you must either correct the error and restart the Launchpad, or click Refresh and clear the selection of the product that failed.
If you are unable to install the failed product, complete the following steps:
- Refer to the readme file readme.html for late changes to the installation instructions.
- If the Integration Bus component fails to install, check the contents of the installation log file IBM_Integration_Bus_InstallLog.log, which is stored in your installation directory.
  If you accepted the default location during installation, this directory is as follows. The default directory includes the version, release, modification, and fix of the product that you are installing in the format v.r.m.f (version.release.modification.fix):
  Linux
  
  /opt/ibm/mqsi/v.r.m.f
  
  UNIX
  
  /opt/IBM/mqsi/v.r.m.f
  
  Windows 32-bit
  
  C:\Program Files\IBM\MQSI\v.r.m.f
  
  Windows 64-bit
  
  C:\Program Files\IBM\MQSI\v.r.m.f for the 64-bit version of IBM Integration Bus
  
  C:\Program Files (x86)\IBM\MQSI\v.r.m.f for the 32-bit version of IBM Integration Bus
  
  These locations define the default value of install_dir on each platform.
- If the IBM Integration Toolkit fails to install, check the contents of the installation log file YYYYMMDD_TIME.xml, where YYYYMMDD_TIME is the date and time of installation.
- If the IBM Integration Explorer fails to install, check the contents of the installation log file IBExplorer_install.log. The log file is stored in the installation directory.
- If WebSphere MQ fails to install, check the contents of MQV7_install.date_time.log stored in the temp directory of your home directory.
If you are still unable to resolve the problem, then locate the installation debug file, IIB_900x_installer_debug.log, and contact your IBM Support Center.

bu16190_.htm |

Last updated Friday, 21 July 2017