Troubleshooting : IBM Installation Manager and WebSphere Application Server Installation Common Issues

HOW TO CREATE A GREY BOX table rows=1, columns=1, ok put your cursor inside the table right click > table properties click on the 2nd tab for Cell Border Thickness, click 'Set All To 0' click the 3rd tab click the drop-down next to color on the far right, choose the 5th tiny box down (not counting the two big grey boxes) Be sure to use arial in the boxes. If you use monospace, you are much, much more likely to overflow your text out-of-bounds. Its unfortunate, but that's just how the new dBlue renderer works. -->

This article describes common Issues with the IBM Installation Manager and WebSphere® Application Server Installations.

Tab navigation

Learn moreTroubleshoot
Troubleshoot - selected tab,
Collect data

Overview:
This topic contains errors or problems the client might encounter when executing the IBM Installation Manager.
Before moving forward, we recommend updating the Installation Manager to latest fix pack available in order to resolve any known issues that is fixed in later levels.

"Installation Manager and Packaging Utility download documents"

Common Issues:

Updating Installation Manager on a computer that has Internet access fails with CRIMA1003E

[wasadmin@swiss1 tools]$ ./imcl install com.ibm.cic.agent
CRIMA1003E ERROR: The com.ibm.cic.agent package cannot be found.

Explanation: A package cannot be found in the specified repository. User Action: Verify the repository contains the package by using the listAvailablePackages command. As a work around for the command line on any operating system, use the following command: For Installation Manager GUI, follow the guidelines in this technote:

Why do I get the following "SWT Library" load error when I try to start the IBM Installation Manager GUI (graphical user interface)?

./IBMIM
00:00.88 ERROR [main] com.ibm.cic.agent.internal.ui.AgentUI reportStatus
Could not load SWT library. Reasons:
/opt/tws/IBM/InstallationManager/eclipse/configuration/org.eclipse.osgi/bundles/465/1/.cp/libswt-pi-gtk4237.a
0509-022 Cannot load module /opt/tws/IBM/InstallationManager/eclipse/configuration/org.eclipse.osgi/bundles/465/1/.cp/liblibswt-pi-gtk-4237.a.so.
0509-026 System error: A file or directory in the path name does not exist.

swt-pi-gtk (Not found in java.library.path)
/.swt/lib/aix/ppc/libswt-pi-gtk-4237.a
0509-022 Cannot load module /.swt/lib/aix/ppc/liblibswt-pi-gtk-4237.a.so.
0509-026 System error: A file or directory in the path name does not exist.
. continues

IBM Installation Manager is an Eclipse Rich Client Program application based on the open source project found at http://www.eclipse.org. Eclipse changed the window system requirement from motif to gtk on UNIX operating systems. For AIX, this Eclipse window system change requires the gtk libraries to be installed to support the GUI.

If the required operating system graphical libraries are not installed, you can still use the IBM Installation Manager in console mode, command-line mode, or silent mode by using a response file.

Problems with the IBM Installation Manager graphical user interface (GUI) include startup issues, broken icons, PangoLayout errors, JVM crash, and JVM hang issues.

For these common problems and resolutions with the IBM Installation Manager GUI, see the technote referenced earlier.

Why do I get the following CRIMA1137W warning message when I am installing the "WebSphere Application Server" product by using the "IBM Installation Manager"?

CRIMA1137W WARNING: The following packages do not support the 64-bit version of Installation Manager that you are using:
IBM WebSphere Application Server Network Deployment version 8.5.0.0.
If you continue, you might have issues with installation and deployment.
For more information about 64-bit mode support for a package, see the package documentation.

The reason this message occurs is because the 64-bit version of Installation Manager checks each package for 64-bit support. If a package does not support the 64-bit version, you receive a warning.

The existence of the CRIMA1137W warning depends on each IBM package or product being installed. The preceding technote references RAD but this message can also be displayed when the customer is installing other products such as WebSphere Application Server.

If the IBM package or product being installed has dependencies on the 32-bit Installation Manager, such as loading 32-bit shared objects or accessing a specific 32-bit program on the computer, then the package might have a problem installing, updating, or uninstalling.

WebSphere Application Server Version 8.5.0.1 and later can be installed with the 64-bit version of IBM Installation Manager. If you receive the CRIMA1137W warning when trying to install 8.5.0.1 or later than the warning message can safely be ignored.

Can I change my installed WebSphere Application Server instance from 32-bit to 64-bit?

There is not a way to convert or upgrade a 32-bit installation of WebSphere Application Server from 32-bit to 64-bit or vice versa. The only way to achieve this change is to uninstall the 32-bit WebSphere product and reinstall the 64-bit version of the product. However, you can retain the profile configuration by backing up the 32-bit profile configuration and restoring it to the newly installed 64-bit instance of WebSphere Application Server:

To avoid problems, create a backup of the IBM Installation Manager Agent Data and IMShared directories so you can restore back to the original point.

Use backupConfig.sh(.bat) to create a backup of each profile.
Uninstall the 32-bit version of WebSphere and delete the remaining WebSphere directory structure.
Install the 64-bit version of WebSphere into the same directory structure as it was installed before, ensuring all paths remain the same as in the 32-bit installation.

Create the same profiles on the newly installed 64-bit instance of WebSphere as existed in the 32-bit instance.

Re-create the deployment manager profile by using the same cell name, node name, and server name as before.
Re-create all other node profiles by using the same cell name, node name, and server name as before, and federate them to the deployment manager.

See the dW Answers previously provided link for details and steps needed to perform the procedure.

Why am I unable to install a second instance of WebSphere Application Server onto the same operating system but into a different location?

The IBM Installation Manager displays the first instance of WebSphere but it doesn't allow a second instance to be installed.

You can install multiple instances of WebSphere Application Server onto a single operating system that uses the same user ID.
When the customer is installing the WebSphere Application Server, each installation is assigned a "Package Group".
To install another instance of WebSphere, you need to assign it a unique "Package Group" name.
If you are using the Installation Manager GUI, it informs you that another version is already installed, but it also allows it to hit "Continue" to install a second instance.
The "Package Group" name of the second installation instance of WebSphere is assigned an "_number" at the end. Example

If the first installation instance of WebSphere has a "Package Group" name of "IBM WebSphere Application Server v85", then the second installation instance of WebSphere has a "Package Group" name of "IBM WebSphere Application Server v85_1"

imcl listInstalledPackages -verbose
-or-
imcl listInstallationDirectories -long

The previous commands provides a listing of the currently installed packages by this Installation Manager. It shows the current "Package Group" value for the current installations.

Why is IBM Installation Manager 1.8.4.1 failing my virus scan with messages similar to the following?

Not scanned (The file is encrypted) C:\IBM Rational\IM1.8.4.1\agent.installer.aix.gtk.ppc_1.8.4001.20160217_1716.zip
Not scanned (The file is encrypted) C:\IBM Rational\IM1.8.4.1\agent.installer.linux.gtk.s390x_1.8.4001.20160217_1716.zip
Not scanned (The file is encrypted) C:\IBM Rational\IM1.8.4.1\agent.installer.linux.gtk.x86_1.8.4001.20160217_1716.zip
Not scanned (The file is encrypted) C:\IBM Rational\IM1.8.4.1\agent.installer.linux.gtk.x86_64_1.8.4001.20160217_1716.zip
Not scanned (The file is encrypted) C:\IBM Rational\IM1.8.4.1\Test\plugins\com.ibm.cic.agent.core_1.7.11.v20160129_1848.jar

This problem is documented in the following Q&A technote: Why IBM Installation Manager 1.8.4.1 failing virus scan?

This is a known issue with IBM Installation Manager 1.8.4.1. The com.ibm.cic.agent.core_1.7.11.v20160129_1848.jar file listed above contains some encrypted .zip files under the win32 directory. These encrypted .zip files were unintentionally included in the plug-in and have since been fixed in IBM Installation Manager 1.8.5.

Why IBM Installation Manager shows error CRIMC1021W - Potential problems logged in diagnostic download log at file: .

This is usually accompanied by the following message: Exception java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at

java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:97) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:370) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:231) . during socket connection to www.ibm.com/000.000.000.000:443[0.0.0.0/0.0.0.0:0].

It means the Installation Manager is trying to check online repositories or the Passport Advantage website for newer packages. To prevent this, follow the link provided here:
“Installation Manager attempts to connect to internet”
https://www.ibm.com/support/pages/installation-manager-attempts-connect-internet

Why IBM Installation Manager shows Out Of Memory errors

JVMJ9VM035 Unable to allocate OutOfMemoryError
JVMDUMP039I Processing dump event “abort”, detail “” at 2022/08/31 05:57:41 - please wait.
JVM terminated. Exit code=210
/usr/WebSphere80/InstallationManager/eclipse/jre_7.0.100001.20170309_1301/jre/bin/java
-Xms40m
-Xmx128m

The above shows Out Of memory error message confirmed by the Exit code 210 which means it failed to allocate memory. The Max heap size is too small to execute the Installation Manager.

The MaxHeapSize (-Xmx) parameter is too small for the Installation Manager. Open the imcl.ini or the IBM.ini and change the -Xmx parameter to at least 1024m

Is the export display supported?

In order to access the IBM Installation Manager GUI (Graphic User Interface)remotely, it is only supported using VNC as described in the Installation Manager System Requirements page: