Messages and known issues during installation and profile creation

IBM BPM, V8.0.1, All platforms > Troubleshooting and support > Troubleshooting installation and configuration
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.

The following IBM BPM installation and configuration errors appear on Linux, UNIX, and Windows platforms.
Tip: For information about messages that might be generated by the installation of WebSphere Application Server ND, refer to the Business Process Management messages topic.
If you do not see an error message that resembles yours, or if the information provided does not solve your problem, contact IBM BPM support at IBM for further assistance.

: Troubleshooting installation and configuration

Informational messages

The following messages are for information only and do not require any action:

Sample applications feature is not available for installation because the WAS Samples feature is not installed.
Installation Manager cannot remove feature import.productProviders.feature from an installation package that was imported to Installation Manager.
Installation Manager cannot remove feature import.configLauncher.feature from an installation package that was imported to Installation Manager.

Configuration errors were detected during the installation

If installing either the Advanced or Advanced Process Server editions of IBM BPM V8.0.1 with Installation Manager, and you selected to install only the client, you might get the following warning message: The packages are installed with warnings. View Log file
If you see this warning message after installing the client feature of BPM, either the Advanced or the Advanced Process Server edition, on a Windows system with just the client feature selected, examine the logs. If, in the logs, you see the following message, then you cannot use the Windows add or remove programs function to remove the client: 2464 WARNING 27:29.66 com.ibm.ws.exec.command.ExecCommand "C:\IBM\WebSphere\AppServer/util/bpm_configManagerLauncher.bat" cannot be found
To remove the client, use Installation Manager.

An earlier instance exists

When you perform a typical installation of IBM BPM after installing it previously on the same drive, you might see the following message:

An earlier instance exists in drive where DB2 is being installed/BPMINST. Either delete or rename this folder. Press "Re-Validate" button once you have taken these steps.

An earlier instance exists in instance_user_home/instance_user. Either delete or rename this folder. Press "Re-Validate" button once you have taken these steps.
The DB2 instance folder folder already exists at path. Delete the DB2 instance folder folder and then retry the installation.
Delete the indicated folder and click Re-Validate before you continue the installation.
When you perform a custom installation, you might see the following message:

The DB2 instance folder folder already exists at path. Delete the DB2 instance folder folder and then retry the installation.
Delete the indicated folder and run the installation again.

Supported IBM JDK was not found. The IBM JDK shipped with this product must be located at INSTALL_ROOT/JDK. Correct this problem and try again.

If you use symbolic links to point to the IBM Java™ Development Kit (JDK) shipped with the product, or to a JDK found in the PATH environment variable on your system, IBM SDK for Java validation might fail, resulting in a failed installation. This problem is caused by the way IBM SDK for Java validation code detects whether the JDK shipped with the product is the current JDK used for installation.
To resolve this problem, do not use symbolic links in JVMs supplied with the installation image of IBM BPM and remove symbolic links from all JVMs that appear in your system's PATH environment variable.

Warning: Cannot convert string "<type_name>" to type FontStruct

If install the web server plug-ins for WebSphere Application Server, you also install the ikeyman utility. The ikeyman utility is part of the Global Services Kit 7 (GSKit7).
If you issue the ikeyman.sh script on a Linux system, you might see the following message:
Warning: Cannot convert string 
   "-monotype-arial-regular-r-normal--*-140-*-*-p-*-iso8859-1"
   to type FontStruct
You can safely ignore the warning and use the ikeyman utility.

CWWBB0627E error during installation with DB2 Express on Linux systems

When install IBM BPM, IBM Business Monitor, or WebSphere Enterprise Service Bus with DB2 Express on a 32- or 64-bit Linux system, the server does not start successfully. Also, the SystemOut.log file includes CWWBB0627E: Failed to create the database schema.
The problem occurs if you used the Administration server (DAS) user name, which defaults to bpmadmin, instead of the Instance user name, which defaults to bpminst.
This problem can occur in the following situations:

When you use the Administration server (DAS) user name during a Custom installation, in which you create the profile after installation
During a Typical installation with an existing DB2 database

If the problem occurs, the SystemOut.log file contains the following information:
[5/24/11 10:40:27:131 CDT] 00000000 CreateSchemaM E   CWWBB0627E: Failed to create the database schema.
[5/24/11 10:40:27:227 CDT] 00000000 ProcessEngine E
[5/24/11 10:40:27:274 CDT] 00000000 ManagerAdmin I   TRAS0018I: The trace state has changed. The new trace state is *=info.
[5/24/11 10:40:27:499 CDT] 00000000 CreateSchemaM I   CWWBB0625I: Started creating the database schema.
[5/24/11 10:40:27:502 CDT] 00000000 CreateSchemaM I   CWWBB0658I: Schema qualifier is: 'BPEDB'.
[5/24/11 10:40:27:909 CDT] 00000000 CreateSchemaM I   CWWBB0614E: Database schema creation or migration step failure 
  CREATE TABLE BPEDB.PROCESS_TEMPLATE_B_T ( PTID CHAR(16) FOR BIT DATA NOT NULL , NAME VARCHAR(220) NOT NULL , 
  DEFINITION_NAME VARCHAR(220) , DISPLAY_NAME VARCHAR(64) , APPLICATION_NAME VARCHAR(220) , DISPLAY_ID INTEGER 
  NOT NULL , DISPLAY_ID_EXT VARCHAR(32) , DESCRIPTION VARCHAR(254) , DOCUMENTATION CLOB(4096) , EXECUTION_MODE 
  INTEGER NOT NULL , IS_SHARED SMALLINT NOT NULL , IS_AD_HOC SMALLINT NOT NULL , STATE INTEGER NOT NULL , 
  VALID_FROM TIMESTAMP NOT NULL , TARGET_NAMESPACE VARCHAR(250) , CREATED TIMESTAMP NOT NULL , AUTO_DELETE 
  SMALLINT NOT NULL , EXTENDED_AUTO_DELETE INTEGER NOT NULL , VERSION VARCHAR(32) , SCHEMA_VERSION INTEGER NOT 
  NULL , ABSTRACT_BASE_NAME VARCHAR(254) , S_BEAN_LOOKUP_NAME VARCHAR(254) , S_BEAN60_LOOKUP_NAME VARCHAR(254) , 
  E_BEAN_LOOKUP_NAME VARCHAR(254) , PROCESS_BASE_NAME VARCHAR(254) , S_BEAN_HOME_NAME VARCHAR(254) , 
  E_BEAN_HOME_NAME VARCHAR(254) , BPEWS_UTID CHAR(16) FOR BIT DATA , WPC_UTID CHAR(16) FOR BIT DATA , BPMN_UTID 
  CHAR(16) FOR BIT DATA , BUSINESS_RELEVANCE SMALLINT NOT NULL , ADMINISTRATOR_QTID CHAR(16) FOR BIT DATA , 
  READER_QTID CHAR(16) FOR BIT DATA , A_TKTID CHAR(16) FOR BIT DATA , A_TKTIDFOR_ACTS CHAR(16) FOR BIT DATA , 
  COMPENSATION_SPHERE INTEGER NOT NULL , AUTONOMY INTEGER NOT NULL , CAN_CALL SMALLINT NOT NULL , CAN_INITIATE 
  SMALLINT NOT NULL , CONTINUE_ON_ERROR SMALLINT NOT NULL , IGNORE_MISSING_DATA INTEGER NOT NULL , EAR_VERSION 
  INTEGER NOT NULL , LANGUAGE_TYPE INTEGER NOT NULL , DEPLOY_TYPE INTEGER NOT NULL , MESSAGE_DIGEST VARCHAR(20) 
  FOR BIT DATA , CUSTOM_TEXT1 VARCHAR(64) , CUSTOM_TEXT2 VARCHAR(64) , CUSTOM_TEXT3 VARCHAR(64) , CUSTOM_TEXT4 
  VARCHAR(64) , CUSTOM_TEXT5 VARCHAR(64) , CUSTOM_TEXT6 VARCHAR(64) , CUSTOM_TEXT7 VARCHAR(64) , CUSTOM_TEXT8 
  VARCHAR(64) , PRIMARY KEY ( PTID ) ) IN BPETS8K: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: 
  SQLCODE=-204, SQLSTATE=42704, SQLERRMC=BPETS8K, DRIVER=3.61.65.
[5/24/11 10:40:27:912 CDT] 00000000 CreateSchemaM E   CWWBB0627E: Failed to create the database schema.
[5/24/11 10:40:27:912 CDT] 00000000 CreateSchemaM E   CWWBB0627E: Failed to create the database schema.
[5/24/11 10:40:27:948 CDT] 00000000 TraceBPE      E   
To solve the problem, you can either create a new profile, or you can use the usermod command to add the Administrative server (DAS) user name:
Create a new profile using the -manageprofiles command. Specify the Instance user name, which, by default, is bpminst, for the -dbUserId parameter.
Add the Administrative server (DAS) user name, which, by default, is bpmadmin, to the bpmiadm1 group by running the following command:
usermod -a -G bpmiadm1 bpmadmin