File sync stalls for 60 seconds on about 10% of the files

[ds00424]

Hi there.
I recently upgraded from 2013 to 2019 (running ver 14.0.1.1).
When I do file syncs I am seeing about 10% of the files stall for about 60 seconds and then resume. This happens on either the backup of the file or the copy of the file. I am syncing WebDav to FTP. Needless to say this is very annoying as it makes what should be a quick sync into many minutes. I just synced 88 files and it took about 10 minutes!

What debugging or other info can I provide to help identify the root cause of this issue?

Thanks.
David.

[RiseFly]

This problem may be related to the response speed of the WebDAV or FTP server.
BestSync will not stall without reason.

[ds00424]

Thanks for the quick reply.

I did not see this issue when using BestSync 2013 with the same WebDav and FTP endpoints.
There were some 'stalls' that occurred for a second or two. But never for 60s.

Again, is there some log or debug we can look at to determine the cause of these stalls.
With this issue, I consider the tool unusable.

Thanks.
David

[RiseFly]

You can start the preview of the task to see where BestSync stalls.

[ds00424]

So seems like BestSync was in a bad state. I wanted to create a task to upload to a test area. So I did Edit/Copy an existing task but was unable to then paste. So i created a new task and after configuring each tab -- when i hit OK to save the task, BestSync crashed. When it came back up I had to re activate my license and the task i was creating did not exist. However, i was now able to copy/paste a task and a test task ran as expected uploading 98 files in about 10 seconds. I will keep an eye on this one. Thanks for your quick replies and advice.

[RiseFly]

BestSync newest version 14.0.1.6 has fixed a bug that may cause crash, please update to last version, the problem may have been fixed.

[sanavigupta]

Great Post

[ds00424]

Ah good. Thanks for the update.
I just saw it again on 14.0.1. So i uninstalled BS and then installed latest -- 14.0.1.6
Will let you know if I see this issue again. Seems like it has to run for a bit.