IBM Support

Cannot start the Process Engine Component Manager (CM) adaptors when the private JRE keystore password used by the CM is changed.

Technote (troubleshooting)


After the user changed the private JRE keystore password, they could not start CM adaptors.


When trying to configure the https connection for Content URI in the Component Manager Process Task Manager (PTM) after the CM private JRE keystore password has been changed, get the following similar errors reported in the PTM CM console:

    java.lang.Exception: com.filenet.api.exception.EngineRuntimeException: FNRCA0031E: API_UNABLE_TO_USE_CONNECTION: The URI for server communication cannot be determined from the connection object...

    Root Cause:

    IBMKeyManager: Problem accessing key store Keystore was tampered with, or password was incorrect

    at filenet.vw.apps.taskman.integrator.VWManagerNode.start(

    at filenet.vw.apps.taskman.integrator.VWManagerNode.actionPerformed(

    at filenet.vw.apps.taskman.VWTaskCore$



The private JRE keystore password used by the Component Manager is changed from its default changeit password.

Resolving the problem

To get CM to work with the new keystore password, you need to do the following:

  1. Edit ...\Router\
  2. Add<pw><pw>
  3. Perform the following to each CM instance :
    • select the connection point related CM, under the 'ComponentManagers' node
    • go into the 'Advanced' tab for the CM
    • in the JRE Parameters, add the following:
This should allow the CM to work with the keystore that has a different password. Note that this issue will be addressed in Process Engine 5.0 patch 2. Refer to defect ecmdb00962675/APAR PJ39095.

Document information

More support for: Case Foundation
Process Engine

Software version: 5.0

Operating system(s): AIX, Linux, Windows

Software edition: All Editions

Reference #: 1505196

Modified date: 10 October 2011

Translate this page: