KB441604: 'content service is not initialized correctly' error occurs when connecting to history list database with 'EnableBatchSupport=1' defined

 

Symptom 

'Content service is not initialized correctly' error occurs when connecting to history list database with 'EnableBatchSupport=1' defined in the connection string parameter of DB2 database instance.
 
Following errors are observed in DSSErrors.log:

[PID:15138858][THR:258][Database Classes][Error] Connect failed. Error type: Odbc error. Odbc operation attempted: SQLDriverConnect. [HY000:2704: on SQLHANDLE] [Strategy][ODBC DB2 Wire Protocol driver]Error parsing connect string at offset 37. Connection String: DSN=xxx;UID=xxx;.[PID:15138858][THR:258][Database Classes][Error] Failed to connect to data source. Error message: Connect failed. Error type: Odbc error. Odbc operation attempted: SQLDriverConnect. [HY000:2704: on SQLHANDLE] [Strategy][ODBC DB2 Wire Protocol driver]Error parsing connect string at offset 37. Connection String: DSN=xxx;UID=xxx;.[PID:15138858][THR:258][MSql][Error][0x80041404] Database error <5>: Connect failed. Error type: Odbc error. Odbc operation attempted: SQLDriverConnect. [HY000:2704: on SQLHANDLE] [Strategy][ODBC DB2 Wire Protocol driver]Error parsing connect string at offset 37. [PID:15138858][THR:258][Kernel][Fatal] MsiSessionManager::InitHLContentService(): History List Content Service initialization fails. Please check the database error above for more information and examine if the History List database has been populated/upgraded with the latest script, return error 0x80041404. 

 

Steps to reproduce

1. Configure a DB2 database as a HL DB.
2. Create HL DB connection and create HL database instance.
3. In Developer, right-click the History List database instance and select 'Edit'.
4. Select 'Modify' for the History List database connection.
5. Navigate to the advanced tab.
6. In the field 'Additional connection string parameters', enter 'EnableBatchSupport=1'.

 
 

Cause

This is a known issue with Strategy 10.x.
 
 

Action

This issue has been fixed in Strategy 10.2. Upgrade to this version to take advantage of the fix.
 
 
 

Workaround

1. Remove the 'EnableBatchSupport' from the connection string parameter at the database instance level.
2. Enable batch support through the DSN parameters in the odbc.ini .