Resolving problems when you install IBM App Connect Enterprise

Work through the advice that is provided to help you to deal with problems that can arise when the product is installed on a distributed platform, such as on a Windows, or Linux® system.

About this task

The following list describes problems that you might experience when you install IBM® App Connect Enterprise on a distributed platform, with a corresponding solution or workaround.

You are prompted for the location of files during installation

Procedure

  • Scenario: During the installation of IBM App Connect Enterprise, you are prompted to provide the location of certain installation files.
  • Explanation: It is likely that your installation package is truncated and that files are missing.
  • Solution: Check the size of the installation package and download another copy of the package if it is not the expected size.

The installation fails

Procedure

  • Scenario: You have problems during the installation of IBM App Connect Enterprise.
  • Solution: If the installation fails, you should receive an error message with an error code and a link to the log file where the error is explained. If you cannot identify the problem and need to contact your IBM Support Center for assistance, the following are the log files that you should send to your IBM Support contact:
    • %LOCALAPPDATA%/Temp/IBM_App_Connect_Enterprise_12.0.n.0_timestamp.log
    • %LOCALAPPDATA%/Temp/IBM_App_Connect_Enterprise_12.0.n.0_timestamp_1_IIBCommonInstall.log
    • %LOCALAPPDATA%/Temp/IBM_App_Connect_Enterprise_12.0.n.0_timestamp_2_IIBServerInstall.log
    • %LOCALAPPDATA%/Temp/IBM_App_Connect_Enterprise_12.0.n.0_timestamp_3_IIBToolsInstall.log
    where timestamp is the date and time of the installation.

The installation process is interrupted

Procedure

  • Scenario: You are installing IBM App Connect Enterprise but the process is interrupted before the installation completes.
  • Explanation: The process might be interrupted because of a problem, such as a power failure.
  • Solution: Restart the installation wizard. If the installation was interrupted by a power failure, the installation wizard automatically restarts when you restart the computer. The installation process continues from the point where it was interrupted, and program files that are already installed are not reinstalled. Do not change the location of the installation directory when you restart the installation, otherwise the program files are split across the two directories, and IBM App Connect Enterprise will not work correctly.

Firewall software reports attempted internet access from an unexpected program

Procedure

  • Scenario: During installation of the IBM App Connect Enterprise, your firewall software reports attempted internet access from an unexpected program.
  • Explanation: Internet access is not required to complete the installation of the IBM App Connect Enterprise. However, the product might install an updated Microsoft C runtime library or updated version of the Microsoft.NET framework. These components might attempt internet access during the installation, which might cause firewall software to report a warning.
  • Solution: This is normal behavior and the installation completes successfully whether you allow access or not.

MSVCP120.dll missing message is issued

Procedure

  • Scenario: During installation of IBM App Connect Enterprise, a pop-up window is seen that states mqsisetsecurity.exe has stopped working. Clicking the details in the pop-up window shows that the MSVCP120.dll file is missing.
  • Solution: Download and install the Microsoft Visual C++ 2019 Redistributable Package.

You experience display problems when you start the IBM App Connect Enterprise Toolkit

Procedure

  • Scenario: You unpacked IBM App Connect Enterprise, started the IBM App Connect Enterprise Toolkit, and see one of two commonly reported errors.
  • 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.