sync client is locking files and causes other software to crash

[jkischel]

Hi folks,

our company, M&M software GmbH from Germany, is developing the industrial automation developing software e!COCKPIT for the WAGO group and therefore we’re handling the pure technical support for that application.

From time to time, some of our customers that using your [Windows] Dropbox synchronization client report that our application crashes when Dropbox starts to synchronize files. Our developer team tracked down the problem to that point that the Dropbox sync client seems to lock the files exclusively [and therefore, "stealing" access] when synchronizing them with the Dropbox server so our application cannot access its own files in that moment.

As the core of e!COCKPIT is based on a third party compiler software (CODESYS), we cannot just catch the exception and everything is fine because a data loss would occur in that moment and corrupted files would be the result. Bad idea. Also, the manufacturer of CODESYS told us that they will not fix this as the problem origin comes from an external source and is also very specific.

Is there anything we could tell the customers how to configure your sync software to perform a more ‚friendly‘ way of accessing files, some settings in the application, a hidden registry key or whatever? Would a third party client that is not from Dropbox solve that problem (if yes, which one?)? Note that we in this project are no active dropbox customers and we're not using the service at all, so we would just forward that information to the related customers in hope that it would help them anyway.

Kind regards,

Jan Kischel

software tester and technical support

M&M Software, Germany

[Walter]

Hey @jkischel, welcome to the Community!

The best way to tackle this would be to have your clients pause syncing (or even quit the app) when working on those files through your own app and resume syncing or re-launch our desktop app when they're done with their edits.

I hope this helps!

[Anthony O.4]

I have this same issue with a backup application named Backup4All.   I purposely backup some files to a dropbox folder.  It will fail about 50% of the time with a file locking error if Dropbox is running.   If I pause the sync then it succeeds.

========================================

Backup aborted. Reason:

Could not copy

"C:\Users\******\Softland\Backup4all

9\Catalogs\BackupFile(3).bkc" to "D:\Dropbox\Backups\BackupFile.bkc".

The requested operation cannot be performed on a file with a user-mapped section open().

========================================

This is supposed to be an early morning automated backup so manually pausing dropbox is not an option.

There is an existing request for an API or command-line interface to pause the sync to cover these situations.

https://www.dropboxforum.com/t5/Dropbox-ideas/Can-we-have-the-Command-Line-Interface-for-Windows-Mac...

It is possible to do a task kill on the dropbox sync service followed by a restart but that might create more problems than it solves.

[grimhike]

So the suggested answer from a Dropbox agent is manually turning off Dropbox? In other words, "STOP USING OUR PRODUCT when it causes a problem because we're not going to fix it." What a great solution!