It's all about the answers!

Ask a question

Error message background task CRJAZ1992E

Tobias Burkhardt (181814) | asked Jul 08 '13, 3:44 a.m.
retagged Jul 08 '13, 5:17 p.m. by Jennifer Cianchetta-Riordan (2512)


what does the error message mean: "CRJAZ1992E The "" task could not be completed and is now unscheduled. Error details: "CRJAZ0548I Failed to prepare the txn mode."". The error message is displayed in the Diagnostics of the Jazz Server by Background Task. We had the same error on another server but after a restart of the jts.war application the error doesn't appear.

Thanks & Regards


Wendy Murphy commented Aug 14 '13, 9:07 a.m.

We just starting getting this error as well since upgrading to 4.0.3. We are running Windows Server 2008 R2, Windows SQL Server 2008 R2 and Websphere.

Accepted answer

permanent link
Simon Eickel (1.1k75457) | answered Jul 10 '13, 10:28 a.m.
edited Jul 10 '13, 10:31 a.m.
Hi Tobias,

as a good solution you can see this question:
failed with an unexpected error - the error message is crjaz1411e database connection has been closed check database status

see the last comment: by Madhu Prabhu:

CRJAZ1992E The task "" has failed with an unexpected error which has caused it to be unscheduled. The error message is "Failed to prepare connection". Please check your server logs for details. Once you have addressed the issues, you should restart the server to reschedule this background task.

Resolved the above error by increasing the JDBC Connection Pool Wait time from its defualt value of 3000 to 6000. Ran the diagnostics and no errors reported.


Tobias Burkhardt selected this answer as the correct answer

2 other answers

permanent link
Abraham Sweiss (2.4k1331) | answered Jul 08 '13, 10:46 a.m.
Hello Tobias,

First here is the purpose of that task called out in the exception.
Task that runs periodically to request an update for the most out-of-date  provider cache item that it can find on this server, to support cross-repository process sharing. Changes to a providing project area's
 process should be pushed to consumers immediately, but this task adds  reliability in case that push fails short the error means that this task has failed for one reason or another.  the most likely cause of the failiar may be related to network issues.   To get this task rescheduled, a server restart is required.

permanent link
Michael Toole (31168) | answered Jul 31 '13, 1:09 p.m.
 increasing the JDBC pool wait time didnt fix ours either.. We keep getting this on a regular basis and have to restart service in order to clear it up.

We are running 4.0.3 with DB2

Your answer

Register or to post your answer.