Troubleshooting engine and console installations

If you encounter issues when you are installing the engine and console, these solutions can help you troubleshoot them.
Issue Solution
The installation fails. If the installation fails, review the installation log to determine the cause. The log is named IBM_Control_Center_version_Install.log and is in the installation directory.
When you install maintenance for IBM® Sterling Control Center
Monitor
V5.4 and later on AIX® platforms, if the installation fails with the following systems, you must run the slibclean command as a root user and then repeat the maintenance installation.
Symptom 1: The following message displays at the end of the installation:
IBM Control Center Monitor v5.4 had errors installing to:<<scc_install_location. Check <<scc_install_location/IBM_Sterling_Control_Center_v5.4_InstallLog.log for more information.
The client computer where a console is installed does not recognize the engine name and location when the user attempts to run IBM Sterling Control Center Monitor using Java Web Start. (An error message displays at the console computer that states that IBM Sterling Control Center Monitor cannot be launched. Then, a Java Web Start unable to load resource download error displays.)

Run configCC.bat (Microsoft Windows) or configCC.sh (UNIX). Respecify the domain name and location from which the console computer is to download Web Start files.

When you install IBM Sterling Control Center Monitor on the AIX operating system, you might receive the following error message:
0403-016 Cannot find or open the file
Use the following command to run the installer:
bash CCInstall64.bin