8/6/2025 8:10 AM | |
Joined: 11/4/2022 Last visit: 8/6/2025 Posts: 4 Rating:
|
Synchronization between CMW and Comos hangs This solution is about how to set a hanging synchronizationbetween Comos and Ubik running again. It may occur that synchronization problems between CMW and Comos happen.If we use Ubik Enterprise Server instead of Comos Enterprise Server, problems are perceived when packs are missing after daily server processing.This is quite rare.A work package gets put to "in work" status on Comos-side automatically when reaching the planned date,on UBIK-side however it is set to the status "in work"but the synchronization to COMOS doesn't happen and stops. The worker sets the activities to“done”which is synchronized to COMOS from UBIK,so COMOS sets the work package to "done"as well. The result is that the nextwork package in line is only being processed in COMOS if the status "in work" is reached. As this step was skipped the recurring work package is "stopped" until manually started again. A simple workaround without negative impact would be creating the follow-up work package on "done" status too if it hasn't been created already. In the above screenshot in thenavigator,we see the work packages that are being processed in Comos MRO. It may happen in rare cases, that a package is not finished and automatically set to "Finished" in this German Screenshot “Fertig”. In this screenshot we see theWorkaround:Set from planned“Geplant”to processingwhich means inwork, “In Arbeit”.If you do that manually, the problem is fixed for thistimeand it usually takes a long time until it happens again. AttachmentHanging Synchronisation between Comos and Ubik.docx (54 Downloads) |
Follow us on