FreeFileSync Forum

600 seconds? that's 10 minutes of *idle* time before RTS reacts to a change. On a busy server this idle time span will never occur.Zenju

Well, that would explain it! I incorrectly assumed it was idle time for RTS itself, so it would sync every 10 minutes.

You're so fast in replying, thank you!

Hi Zenju,

I don't think Server 2012 is supported but FreeFileSync runs fine on it. It's RealTimeSync that I wanted to check with you about. Here are two screenshots, do you see anything wrong with the configuration?

http://i.imgur.com/1OnHh7k.jpg
http://i.imgur.com/dcgnvmV.jpg

I am able to ...

I installed the beta and that fixed the error messages, tested on a couple of known problem files and they synched fine.

I'll wait until it comes out of beta before I install on my server, but everything works great now. Thanks again!

I'm not quite sure why an error occurs in this situation. The only safe thing to say is that it's happening outside of FFS's control and is either a bug in Microsoft's CopyFileEx, or in the network drivers, or by the network server.
It's a CopyFileEx bug in any case, but MS could argue that a file ...

Talking about the (security-) elephant in the room: you posted the .pml file publicly above containing a lot more than what's on the screenshots...Zenju

You're right, and I've deleted it.

I have the same error on new files I tried to sync today. Do you have any advice on how to remedy?

The file copying of "Conor Lynch signature.jpg" fails when trying to copy a file with an alternate data stream called "AFP_Resource". There are two things that are strange:

1. The creation of the ADS "AFP_Resource" on the network share succeeded, so there is no reason why a later step would fail ...

Next time you encounter this issue (and can confirm externally, e.g. via Windows Explorer that it's indeed an unexpected error rather than the source or target file really missing at the time), start up a Process Monitor ( https://technet.microsoft.com/de-de/sysinternals/bb896645.aspx ) trace ...

Next time you encounter this issue (and can confirm externally, e.g. via Windows Explorer that it's indeed an unexpected error rather than the source or target file really missing at the time), start up a Process Monitor ( https://technet.microsoft.com/de-de/sysinternals/bb896645.aspx ) trace ...

Next time you encounter this issue (and can confirm externally, e.g. via Windows Explorer that it's indeed an unexpected error rather than the source or target file really missing at the time), start up a Process Monitor ( https://technet.microsoft.com/de-de/sysinternals/bb896645.aspx ) trace ...

Have you tried using Windows Explorer to copy the files and see if that works?
Thank you for replying Zenju.

As a workaround to get all my files copied over, yes. I copied them from a full backup taken with BackupAssist into the NAS folder where I wanted them to reside for the 'sync' backups ...

Some more info:

Left (source) is the file server that FFS is installed on. Right (destination) is a Synology NAS shared folder, which is a mapped drive \\ipaddress\sharename. I have also tried it without mapping the drive and using \\ipaddress\sharename and \\servername\sharename.

The files themselves are there, I am an administrator on the file server its being synced from (and to) and the Administrators group has Full Access.

It isn't hidden and isn't read-only. If I choose to Ignore this and the other files that I receive the same error on, the sync completes with those ...