Dropbox file synchronisation replaces all spaces by %20 and duplicates them infinite

[viewonit]

Hi,

We use BestSync 2017 (version 12.0.2.4 64Bit) to sync our Dropbox folder to a server directory where Dropbox can't be used.

The last days, when we used Auth02 to reauthenticate BestSync with our Dropbox account, all files that contain a space in the filename, is duplicated and shown as %20 as the space. The script is running as a service and synchronises every 15 minutes, so every 15 minutes each file is added again and again and again with %20 or %2520 or %252520, etc.

Is this a known problem and can this be fixed?

Please let me know!

Kind regards,

View on IT

[RiseFly]

BestSync 2018 (VER13.0.0.4) has been released, the version has fixed this problem, please try it.

[viewonit]

During the preview only a few files and folders are still syncing with the %20 spaces in their names. So not all of the files and folders are doing this anymore, only a few left.
I checked to be sure that these files were no longer on the server and syncing towards Dropbox, this wasn't the case.
The preview is now running, after that we will see wether it is fixed indeed.

[viewonit]

It's working now, thanks!

[viewonit]

Hi,

Here I am again, it's actually isn't working for the full 100%. Here's what's happening:
Files are syncing just fine, the spaces are fine and the syncing is fine. But when I create a subfolder on the server in a folder with a space in the name (for example I create the folder "2017" inside the folder "testfolder new", on the server), the primary folder is created again in Dropbox with the %20 encoding, and the subfolder and all new or changed files aren't created but are failing with error message "409 Conflict".

Can you look at this issue again? Please let me know, thanks.

Kind regards,

View on IT

[viewonit]

Hi,
Can you give me a reply on my ticket? The problem doesn't seem to be solved completely..

[RiseFly]

Please delete or rename all the old files or folders that contain %XX encoded characters in the server, before the synchronization.

[viewonit]

I already did that, also I created a new folder called "Test New" on the local server but this folder is then synchronized to Dropbox with again the %XX encoding characters. So it then looks like "Test%20New" in the Dropbox.
I also installed the newest version BestSync 13.0.0.5, but this doesn't solve the problem either.

So, the new folder is still synced to the Dropbox using the %XX character encoding. Much files and folders which were moved locally on the server aren't synced at all and are showing error message "409 conflict". For the rest, it's doing nothing at all.

Maybe you can check with me what's wrong, or maybe I can send a private message with a log or something to solve the problem?

[RiseFly]

BestSync 2018 version 13.0.0.6 may have been fixed the problem, please download and try the new version.