Configuring the object stores failed

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Draft comment:
This topic was viewed 39 times since its publication
If configuring the object stores fails, you can either re-tune your database or increase the database transaction timeouts.

Symptoms

An error occurs while running Configure the Case Management Object Stores. The task fails because of the following error:

The case management add-ons cannot be installed in Content Engine. The installation of the AddOn 5.3.2 Case Manager Target Object Store Extensions into the object store TOS failed. The installation report follows: PostImportScriptMethod failed with exception: There was an error running the script. Message was: Wrapped com.filenet.api.exception.EngineRuntimeException: FNRCE0075E: E_TRANSACTION_FAILURE: A transaction failure has occurred due to an invalid state or timeout. The current transaction state is STATUS_MARKED_ROLLBACK and it was expected to be active failedBatchItem=0 (#256).

Causes

Installing the Case AddOns extensions took longer than the maximum allowed length for a database transaction. This triggered a timeout, a transaction failure, and the rollback of the transaction.

Resolving the problem

To ensure that the transaction completes within the timeout, you can apply one or both of the following procedures:
Retune your database so that the transaction completes within the timeout period
Check the tuning for your database, as described in Tuning an IBM® DB2® database for IBM Content Cortex components External link opens a new window or tab
Increase the application server timeout settings
Set the application server timeout values to at least 600 seconds. The following sample settings are for WebSphere® Application Server Version 8.5.2:
  • Servers > Server Types > WebSphere application servers > Configuration tab > Container Settings > Container Services > Transaction service > Total transaction lifetime timeout
  • Servers > Server Types > WebSphere application servers > Configuration tab > Container Settings > Container Services > Transaction service > Maximum transaction lifetime timeout
  • Servers > Server Types > WebSphere application servers > Configuration tab > Container Settings > Container Services > ORB service > Request timeout
  • Servers > Server Types > WebSphere application servers > Configuration tab > Container Settings > Container Services > ORB service > Locate request timeout
    Note: For WebSphere Application Server Version 8.5.2, the maximum value for the locate request timeout is 300.
  • Resources > JDBC > Data sources > [Content Engine or Case Manager data source name] > Connection Pool properties > Connection timeout
  • Resources > JDBC > Data sources > [Content Engine or Case Manager XA data source name] > Connection Pool properties > Connection timeout
In the Case configuration tool, rerun the "Configure the Case Management Object Stores" task.