IBM Domino Designer stuck on 'Sync with ODP...'

Question

I am using GitLab in combination with Sourcetree. Every time I want to commit something, I would go to my Domino Designer and right click the database, click Team Development and use 'Sync with ODP...'.

Most of the time everything works perfectly fine but sometimes the synchronization dialog pops up and just wont go away. In my Sourcetree I can see that some files are waiting to be commited but those files are not all.

So the dialog shows up, wont go away and says "Progress information" "Exporting..." and thats it.

There is no "use in background" button there and the 'cancel' button is disabled.

At this point the only thing I can do is to shut down the Designer using the task manager but the problem still wont go away even after restarting my computer and VirtualBox which I am working on (The designer runs on the VM). The only thing that changes: It sometimes gets stuck "later" in the progress.

I have read the designer hangs often due to automatic synchronization. In my case this feature is disabled.

Is there someone who can tell me what causes this problem and how I can fix it? - Thank you in advance

(The synchronization is in progress for roughly four hours now, with no change)

Answer 1

We are using Domino Designer and Sourcetree in combination with Mercurial and Bitbucket for about a year now. We suffered a lot of difficulties: "hanging" sync, corrupted custom controls, missing files, lot of stress etc.

What I did find out: most of the syncing problems have something to do with the file IconNote in the resources. Sometimes the associated source contains another version of this resource, so it creates an IconNote.orig. Whenever this file exists, the syncing will go wrong. I guess that IconNote.orig isn't allowed in Resources and so the syncing stops without any warning(!) and often corrupted files.

It took me a very long time find out, but now I know: If IconNote exist in the Git, I delete it instantly! Syncing goes well aftwerwards.

Answer 2

Are you able to track it down to a specific design element? If there is a corruption in the DXL, the export to the ODP will probably fail. In Package Explorer you can use the "Open With..." right-click menu option to open as XML. Similarly, using the menu options to export as DXL might also highlight any corruption in DXL. Also, is the NSF local or on a server. If it's on a remote server, that may impact the performance of syncing to an ODP (which will be local).