It's all about the answers!

Ask a question

Impossible to save Work item because of conflict

Tim De Becker (1026) | asked Jun 20 '14, 3:40 a.m.

Our team in encountering a problem with specific work items.

We have a work item 372 that is linked with a second work item 3780 from another project area.
When we try to save modifications on those two work items we have the following error:

After a refresh of both Work items it is still not possible to save the modification. There's nothing in the server log related to that problem.

We are using RTC v4.0.5.

Thanks in advance for your help!


sam detweiler commented Jun 20 '14, 7:42 a.m. | edited Jun 20 '14, 7:44 a.m.

we saw this a few times on 4.0.4 too.. only  a server restart resolved the problem.
in our case, the workitem was a few weeks old, and was last updated the day before the problem occurred.

I no longer work there, so don't know if they resolved the problem thru support.

Accepted answer

permanent link
Don Yang (7.6k21105137) | answered Jun 23 '14, 3:04 a.m.
Hi. Tim

There are some reports on the similar issue you are encountering and the possible causes are:

1)Server cache
2) ETL jobs running or failure

For 1), you need to restart the server
For 2) Waiting for ETL to complete and fixing any ETL problems required(if ETL job has any issues, you can check with ccm-etl.job to see if there is any clues).


Tim De Becker selected this answer as the correct answer

4 other answers

permanent link
Tim De Becker (1026) | answered Jun 24 '14, 1:35 a.m.
edited Jun 24 '14, 1:36 a.m.

Thank you for your help, restarting the server resolved the problem.
I hope we will not have this issue too often... 


permanent link
Matthew Owenby (23811) | answered Nov 17 '15, 11:57 a.m.
We are having this problem and a server restart did not resolve the issue.  Our ETL jobs appear to be running without incident.  Are there any other options besides filing a support request with IBM?

Nate Decker commented Jan 05 '17, 11:58 a.m.

 In our environment, one of our custom follow-up actions causes this to happen in certain circumstances. To test whether that is a factor, try using a role where no pre-conditions or followup actions are enabled.

permanent link
sam detweiler (12.5k6191201) | answered Nov 17 '15, 12:02 p.m.
 I don't know of any other solution.

permanent link
Chao Wang (225112) | answered Nov 17 '15, 12:27 p.m.
A defect was opened for this issue. See more details below:

Your answer

Register or to post your answer.