It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,432
×6,020

question asked: Feb 26 '18, 4:49 p.m.
question was seen: 2,615 times
last updated: Feb 26 '18, 7:56 p.m.

Related questions

CRJAZ2388E The background process that synchronizes user data between servers could not be completed.

0
madhu sudana (31●1●18) | asked Feb 26 '18, 4:49 p.m.

CLM Version 5.0.2 application was down and it is showing following error message on System Out file. Please help on suggesting proper fix.



[2/26/18 14:39:04:551 CST] 0000018f SystemOut     O 2018-02-26 14:39:04,551 RQM [qm: AsynchronousTaskRunner-0 @@ 14:38] ERROR com.ibm.team.repository                             - CRJAZ2388E The background process that synchronizes user data between servers could not be completed. The synchronizer will attempt the synchronization again.
[2/26/18 14:39:19:571 CST] 0000018f SystemOut     O 2018-02-26 14:39:19,571 RQM [qm: AsynchronousTaskRunner-0 @@ 14:39] ERROR com.ibm.team.process                                - CRJAZ1451E The RequestRemoteEnterpriseProcessUpdatesTask task from the com.ibm.team.process component could not be completed and will be rescheduled.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Don Yang (7.7k●21●114●139) | answered Feb 26 '18, 7:56 p.m.

You may want to check with the discussion in this post:

https://jazz.net/forum/questions/129901/error-shuting-down-the-clm-server

Basically it could be jts server is down while qm is trying to sync the user with jts and throws the error trace.
It seems it won't be fixed per:
https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=348170

I see this message quite often in ccm.log, qm.log as well and I don't think it will cause any problem(it is a result of some other happening not the cause).

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.