It's all about the answers!

Ask a question

CC Synchronizer fails with message "not found"


Simon Eickel (1.1k75457) | asked Apr 19 '13, 3:36 a.m.
edited Apr 19 '13, 3:37 a.m.
Hello my friends,

one more little error message I'm getting since some days when trying to synchronize between RTC and CC:
 

But cannot understand this message as in RTC this component exists and has data inside and in CC the folder exists has the attribute attached and the branch. So everything should be fine.
The workspace the error message specifies is not there - thats true. But why?

In this stream I synchronize 15 components from RTC to CC and just one of them throws this message.
Is there some kind of a limit that only a special number of files or components can be synchronized?
Or do you have some other ideas what could be wrong?
There is enough disc space left.

Greetings,
Simon

2 answers



permanent link
Simon Eickel (1.1k75457) | answered Apr 19 '13, 8:50 a.m.
Hi There,

I'm still not sure why this error messages happens and blocks my synchronizer but I was able to resolve it.

What did I do? One could say I reestablished synchronization. This means I delete the branch on all elements (cleartool find . -exec "cleartool rmbranch -force \"%CLEARCASE_PN%\"") and removed all clones on the component (ccc.exe clones -c <component> -r <repository> -X -u <adminuser> -P <password>).

After this was done I recreated the branch containing zero elements (cleartool find . -exec "cleartool mkbranch -nco -nc <branch> \"%CLEARCASE_PN%\"") and restarted synchronization.

This worked now.

So ... what did I learn - again?
It's often a good idea to delete all information of this (clones etc.) and begin from the scratch ...

Greetings,
Simon

permanent link
Masabumi koinuma (46115) | answered Apr 19 '13, 10:10 a.m.
JAZZ DEVELOPER
Hi Simon, can you attach the stack trace file when you see the error?
Is this a case when you add TC.Facade component-root as a sync-root from the RTC-side?

Comments
Simon Eickel commented Apr 22 '13, 1:47 a.m.

Hi Masabumi,

unfortunately I don't have the stacktrace anymore.
Next time this problem occurs I will post it here.

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.