IBM BPM, V8.0.1, All platforms > Troubleshooting and support

Troubleshooting installation and configuration

You can diagnose problems when the installation and configuration of IBM BPM is unsuccessful.

Procedure

1. Read any error messages from the installation process.

   See the following topic for an explanation: Error messages: installation and profile creation and augmentation. If the message corresponds to any of those described, correct the problem, clean up any installed portions, and try to reinstall.

2. If the installation of WebSphere Application Server ND was not successful, check Troubleshooting installation in the WebSphere Application Server ND information center and use the information found there to correct the problem before attempting to reinstall IBM BPM.

3. If the installation of WebSphere Application Server Feature Pack for SCA with the Service Data Objects (SDO) feature not successful, check Troubleshooting installation in the WebSphere Application Server ND information center and use the information found there to correct the problem before attempting to reinstall IBM BPM.

4. If the installation of WebSphere Feature Pack for Web Services was not successful (and installation of WebSphere Application Server ND was), check Troubleshooting web server plug-ins installation and removal in the WebSphere Application Server ND information center and use the information found there to correct the problem before attempting to reinstall IBM BPM.

   If a problem occurs during an installation of WebSphere Feature Pack for Web Services as part of the IBM BPM installation, the installation process will not continue and an error message will be displayed.

5. If the installation of IBM BPM was not successful (and installation of WebSphere Application Server ND and WebSphere Feature Pack for Web Services were), check other IBM BPM installation log files. For information about the names, locations, and descriptions of these log files, see Installation and profile creation log files.

6. If you have successfully created a server profile, use the First steps console or the command-line method to start the server.
7. Verify that the server starts and loads properly by looking for a running Java™ process and the Open for e-business message in the SystemOut.log and SystemErr.log files.

   If no Java process exists or if the message is not displayed, examine the same logs for any miscellaneous errors. Correct any errors and try again.

   You can find the SystemOut.log and SystemErr.log files in the following platform-specific directories:

   • 

     On Linux and UNIX platforms: profile_root/logs/ servername

   • On Windows platforms: profile_root\logs\ servername

8. Use the First steps console or the command-line method to stop the server, if it is running.

9. If you want to use a Snoop Servlet to verify the ability of the web server to retrieve an application from IBM BPM, see the step "Start the Snoop servlet to verify the ability of the web server to retrieve an application from the Application Server" in Troubleshooting installation in the WebSphere Application Server ND documentation.

10. Start the administrative console.

11. To resolve any IP address caching problems, see the step about resolving any IP address caching problems in Troubleshooting installation in the WebSphere Application Server ND documentation.

What to do next

On the product support web site, you can review current information about resolutions to known problems, and you can read documents that can save you time gathering the information that you need to resolve a problem. Before opening a PMR, see the IBM BPM support page.

• Messages and known issues during installation and profile creation
  Some of the most commonly found error messages encountered when install can be addressed with actions that resolve the underlying problems.
• Installation and profile creation log files
  Various log files are created during installation and uninstallation of IBM BPM and during profile creation, augmentation, and deletion. Consult the applicable logs if problems occur during these procedures.
• Launching Installation Manager directly on 64-bit systems
  

  You can launch Installation Manager directly, for IBM BPM, IBM Business Monitor, or IBM WebSphere Enterprise Service Bus, on 64-bit systems.

• Warnings about GTK or ulimit on Linux or UNIX when installing or migrating
  On the Linux or UNIX operating system, when you are installing or migrating, you might see a warning about 32-bit GTK libraries or increasing your ulimit.
• Troubleshooting problems creating database tables
  While trying to create database tables for the BPM database and the Performance Data Warehouse database, you might get errors or exceptions that prevent you from creating the tables. Your bootstrap operation also fails.
• Troubleshooting Oracle transaction recovery messages
  

  You must apply special grants for Oracle transaction recovery to work correctly.

• Error running bootstrap command or creating profiles with SQL Server databases
  

  If you are using Microsoft SQL Server databases, and you create the BPMDB or PDWDB databases with a case-sensitive collation attribute, then when you use the bootstrapProcessServerData command to load the databases with configuration data, you will get an error.

  If you are using PMT or manageProfiles create the profile, the profile will be created with partial success, and the profile log file will indicate failure running bootstrapProcessServer.ant.

• Problems testing a connection to a data source in an ND
  In an ND environment, testing a connection to a data source can fail, with the error message UndefinedVariableException: Undefined Variable WAS_INSTALL_ROOT. However, this does not necessarily indicate that you will have run time errors.
• Troubleshooting the launchpad application or First Steps
  

  If the launchpad application or First Steps does not start, try the following troubleshooting tips.

• Diagnosing a failing Ant configuration script
  Determine whether a product installation problem on an operating system is caused by a failing Apache Ant configuration script.
• DB2 log file error: SQL1092N "USERID does not have the authority to perform the requested command or operation"
  After install IBM DB2 Express, if you use the domain user ID to create a new database and tables, you might see an error in the DB2 log files. Follow these steps to enable the domain user ID to access the database.
• Profile creation fails on Windows operating system
  The Profile Management Tool or manageprofiles command on IBM BPM might fail on the Microsoft Windows operating system if it is launched without administrative privilege.
• 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.

• Recovering from profile creation or augmentation failure
  The Profile Management Tool can experience failures when creating new or when augmenting existing profiles. The same can occur using manageprofiles.sh.

  If such a failure occurs, first check the log files as described in this topic, then follow the recovery instructions described, depending on the situation.

• Cluster member startup timeout errors reported in dmgr log
  

  If the deployment environment startup takes longer than the default timeout setting, you will see an exception in the dmgr log. Provided the cluster members eventually start, you can ignore the exception.

• Reinstallation cannot create new profile when using the Typical installation and configuration option
  

  If you try to reinstall the product to the same location using the Typical installation and configuration option, or if you try to reinstall after a failed uninstall, the installation might fail because a new profile cannot be created.

• Resolving a DB2 process load issue
  

  You can encounter unexpected process load issues when running DB2

• Uninstalling multiple server and tooling products causes errors
  Uninstalling multiple products (for example, IBM BPM and IBM Integration Designer) at the same time might cause Installation Manager errors or warnings.
• Installing a snapshot fails when single sign-on has been configured
  Installing a snapshot from IBM Process Center to IBM Process Server can fail if single sign-on has been configured.
• Installing a snapshot fails after message confirms installation
  Installing a snapshot on IBM Process Center has a message that confirms the snapshot is installed and then moments later issues a message claiming the installation failed.

Troubleshooting and support for IBM BPM