Installation troubleshooting

This section identifies many installation troubleshooting tips. Search through this section to find solutions to many common problems.

You can find the latest troubleshooting tips in the Support page (http://www.ibm.com/support/search.wss?rs=802&tc=SSSRR3&q=6.2).

Installation and profile creation log files
Various log files are created during installation and uninstallation of IBM Business Monitor and during profile creation, augmentation, and deletion. Consult the applicable logs if problems occur during these procedures.
Installation fails due to errors in stopping and starting the WebSphere Application Server
The installation process must stop and start the WebSphere® Application Server (the server that the IBM Business Monitor server is being installed onto) several times during installation. If the WebSphere Application Server does not stop successfully, the installation process fails.
Launchpad fails to start
If the launchpad fails to start, check the following list of supported browsers and AIX® and Windows issues.
Application problems in the WebSphere Application Server administrative console
After the Monitor Server component installation, the Monitor Action Manager administrative console pages do not load, and the IBM_WBM_ACTIONSERVICES Enterprise Application does not start. These are applications in the WebSphere Application Server administrative console.
Database creation failure
If the IBM Business Monitor database is on a remote server and is already catalogued on the local machine, the database installation fails if you try to install the database again.
Debugging JDBC Data Sources in IBM Business Process Manager
The IBM Business Monitor installation finishes, and the JDBC data source returns an error when tested in the administrative console.
Redhat Enterprise Linux 5 Server installation fails
On the Redhat Enterprise Linux 5 Server, if your installation of IBM Business Monitor, WebSphere Portal, the portlet-based dashboards, or an application results in an Installation partially success message, or you receive an exception that indicates that the process opened too many files, you must modify the value of the nofiles parameter.
CWWBB0627E error during installation with DB2 Express on Linux systems
If the server does not start successfully when you install IBM Business Monitor with DB2 Express on a 32- or 64-bit Linux system, create a new profile or use the usermod command to add the Administrative server (DAS) user name.
Cannot find Profile Management Tool
The Profile Management Tool is not included with Business Monitor if you are running Solaris in 64-bit mode. The Profile Management Tool is also not available with Business Monitor for z/OS®.
Profile creation fails on Windows operating system
The Profile Management Tool or manageprofiles command on IBM Business Monitor might fail on the Microsoft Windows operating system if it is launched without administrative privilege.
Errors when creating or augmenting a profile
When you create a new IBM Business Monitor profile or augment an existing profile with IBM Business Monitor, a result code of INSTCONFSUCCESS, INSTCONFPARTIALSUCCESS, or INSTCONFFAILED is reported. A technote is available to help you interpret the meaning of a partial success or failure result.
Eliminating profile creation OutOfMemoryErrors on Solaris and HP-UX
When you are creating an IBM Business Monitor profile on a Solaris or HP-UX operating system, an out of memory error (java.lang.OutOfMemoryError: PermGen space) might occur and hang the profile creation. You must update the value for the MaxPermSize Java virtual machine (JVM) parameter.
Eliminating runtime server OutOfMemoryErrors on Solaris and HP-UX
When you are starting an IBM Business Monitor server on a Solaris or HP-UX operating system, an out of memory error (java.lang.OutOfMemoryError: PermGen space) is reported and the server does not start successfully. You must update the value for the MaxPermSize Java virtual machine (JVM) parameter.
Remote messaging engine will not start after configuring a remote bus for Process Server 6.0.2
If you are using a Cloudscape database with the Process Server 6.0.2 and the messaging engine will not start after running the ConfigRemoteMonitorBus.bat or ConfigRemoteMonitorBus.sh command, refer to the instructions to delete the service integration bus Cloudscape database.
First steps console fails to start on Windows operating system
The First Steps console on IBM Business Monitor might not launch on the Microsoft Windows operating system when Mozilla Firefox is set as the default browser. The First Steps console either does not start or immediately closes.
Server does not start and you cannot create a Java virtual machine
If your server will not start and your native_stderr.log file contains a JVMJ9VM015W message, which indicates that you could not create the Java virtual machine, and if your environment is a Windows 2003 Server, the cause might be a known Microsoft issue.
Missing DLL files on startup
If you use an existing DOS window to start an application that existed prior to installing IBM Business Monitor, the server runtime environment might be missing path statements that point to the newly installed software. Error messages posted to the logs will indicate missing DLL files.
Exceptions in FFDC log
You might see exceptions in the First-Failure Data Capture (FFDC) log that are generated for IBM Business Monitor. You might also see these exceptions logged in your system logs.
Reinstallation cannot create new profile
If you try to reinstall the product to the same location, or if you try to reinstall after a failed uninstall, the installation might fail because a new profile cannot be created.
Successful installation reported after profile creation failure
If the profile creation step fails during a custom installation, the failure is not recognized by Installation Manager, which reports a successful installation. This problem occurs only on Windows platforms.
Troubleshooting the z/OS installation and configuration
Use this information to help you assess and correct problems that can occur if the product installation or configuration has not been successful.

Parent topic: Troubleshooting

Related reference:

WebSphere Business Monitor Technotes