Dealing with common installation problems

Use the advice given here to help you to resolve problems when installing WebSphere® MQ File Transfer Edition.

Delays when installing

When you install WebSphere MQ File Transfer Edition, you might experience a delay while the installer checks the available space on your system. If you are using the graphical installer, the delay occurs while you are waiting for the Pre-Installation Summary page to display. This delay might be several minutes long depending on your operating system and network drive configuration. The delay is caused by the installer checking available space on your system, which can take longer if you have configured network drives. This delay does not indicate a problem with the installation process; wait for the installation to complete as normal.

Errors when installing

  • If you install V7.0.3 or earlier, you might see one of the following errors:
    • The installer is either corrupt or has not been launched from the original 
      media. Ensure that the original media is being used.
    • Please insert WMQFTE or type its location. 

    These errors can occur when you extract installation files from the eAssembly image but change the original directory structure. You must maintain the following directory structure:

    Disk1/version.ini
    Disk1/InstData/Resource.zip
    Disk1/InstData/MediaId.properties
    Disk1/InstData/VM/install.bin

    If you are installing V7.0.4 or later, there is no requirement to maintain a specific directory structure.

  • On UNIX, if the console or silent installer produces the following error message:
    [--------Invocation of this Java Application has caused an InvocationTargetException.
    This application will now exit. (LAX).
    
    
    Stack Trace:
    java.lang.NoClassDefFoundError: sun.awt.X11GraphicsEnvironment (initialization failure)
    at java.lang.J9VMInternals.initialize(J9VMInternals.java:132)
    this generally indicates that one or more of the X client libraries that are required for the installer to run could not be found on the system. These must be present even though you are not using the graphical installer.
    Note: On 64-bit systems, install the 32-bit version of the library if it is available.
    Ensure that the following libraries are installed (where applicable to your platform), typically in /usr/lib/:
    • libXp.so.6
    • libstdc++.so.5
    • libX11.so.6
    • libXtst.so.6
  • On Linux, if the console or silent installer produces the following error message:
    [-------------Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX)
    
    	Stack Trace:
    	java.lang.UnsatisfiedLinkError: fontmanager (libX11.so.6: cannot open shared object file: No such file or directory)
    	at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:986)
    this indicates that a required library libX11.so.6 could not be found on the system, however this library is needed for the installer to run. Even if you are installing on 64-bit Linux (x86-64) and or if you are running in console mode, the 32-bit version of the library is still required.

    To resolve this error, ensure that the 32-bit version of the library libX11.so.6 is present on the system.

    This library is provided by the packages with names of the format in the following examples:
    • For example, for RedHat Enterprise Linux: libX11-x.x.x-x.xxx.i686
    • For example, for SLES 11 Linux: xorg-x11-libX11-32bit-x.x-x.x.x.x
  • If the installer defaults to a console installation even though the graphical mode is available, check that the DISPLAY environment variable is set to point to a valid, accessible X Windows server and that the above X client libraries are installed.

Reference Reference

Feedback

Timestamp icon Last updated: Tuesday, 30 January 2018
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/trouble_installer_common.htm