FreeFileSync Forum

You're right, this works like a charm:

:restart
"C:\Program Files\FreeFileSync\FreeFileSync.exe" "C:\Program
Files\FreeFileSync\SyncIL-UA.ffs_batch"
@if not errorlevel 0 (
sleep 2
goto restart
)

Exactly. Same as RTS won't retry sync.

'forgot the error line:
Windows Error Code 64: The specified network name is no longer available.
Info: Generating database...
Warning: Synchronization completed with errors!
Stop (Total time: 00:07:19)

'Tried to implement but this won't work. Looks like FFS won't return
errorlevel, for both .bat and RTS. Log:
Error: Error copying file:
Info: Generating database...
Warning: Synchronization completed with errors!
Stop (Total time: 00:07:19)

And after that sync won't reoccur.

Ok, great, 10nx.

Thanks, Zenju.
However Retry option is still not available for a batch jobs.

1. Yes, but that will leave ffs_tmp files...
3. Sorry, I meant ffs_tmp.

So, will something of this be implemented in 3.7?

Hello Zenju,

I checked the sources, wanted to see if I can commit this change by myself,
but =)
It'll take long to get into code.

Just to make things clear, my changes proposal is:
1. Automatic retry option for FFS's batch processing to overcome "Windows Error Code 64: The specified network ...

Cool, 10nx

Zenju, any ETA please?

Great, thanks!
When will it be released?

Well, in case of retry it can check <Filename>.ffs_tmp* and clean them up.

Zenju, is it possible that you will implement this retry (in batch) option
along with the cleanup in a nearest future?

Well, it does it's job, but after the reconnection and pressing Retry, FFS
leaves ffs_tmp file in the destination.
Also, the retry doesn't work at all if the network failed during the Compare
phase.

I rechecked, FFS doesn't work correctly on bad connection (though does
fantastic job on good connection or locally).
If you could add some robustness to the copy, it would be great (like in MS's
robocopy, it works great on bad connections).

Thanks! Yes, I do understand this...
This indeed would be a great option.

This is the part of the log:
"Windows Error Code 64: The specified network name is no longer available."
This happens due to the bad network connection.
FFS will write the tmp file on the destination and leave it there ...

I don't get any. The batch job is configured to Ignore errors, whilst I need
to silently Retry for every error.

Yup, I'm using the last version.
No man, it's not about "not existing" dir. It's about network outages during
the copy.

Thanks for the reply.

No, I mean the Retry option during synchronization when done from
FreeFileSync. However there is no such option for RealTimeSync, although, I
guess, there should be one. And it should be "Retry for all errors", no pop-
ups.

Hello guys and thanks for the wonderful soft!

Is there a possibility to handle errors in a batch file with the retry. This
would be a great feature for a sync over bad/slow connections.

Thank you for your help in advance.