[Translate:English]
I had the same event and just resolved it.
I think there is a folder or file with the same name in the source folder.
In Jim's case, there may be the following folders or files in "\\office\Users\James\Documents\".
Assumption 1: "My Documents.ffs_gui" and "my documents.ffs_gui".
Assumption 2: "My Documents" and "My Documents.ffs_gui"
I have had the same issue and I hypothesize that it is an error in FreeFileSync that occurs when a file has been changed both in content and in terms of the case of letters in its file name (which can only occur on file systems that do not ignore the difference in case, e.g. Linux, Android or those in many NASes).
I suspect that a file being synced (e.g. perhaps called "Name.Ext") is divided into these stages:
[1] copy to Name.fs_tmp
[2] delete Name.Ext
[3] rename Name.fs_tmp as Name.Ext
I think this error occurs in [3] because there is already a file called "Name.Ext" with a different capitalization which causes the rename to fail. Stage [2] would normally remove this file but I imagine is deleting only files with exactly the spelling Name.Ext.
Example:
So when we update the content of Photo.JPG and simultaneously change its name to photo.jpg it will be sync'ed.
[1] will work fine
[2] will not delete the existing Photo.JPG because it deletes only files called photo.jpg
[3] will fail because the rename can't overwrite photo.jpg (which is the same file as Photo.JPG on
a file system that ignores file case)
If that were the problem it might be fixed in FreeFileSync by using a "normal" delete operation at [2] which should delete photo.jpg if the deletion of Photo.JPG was requested.
]]>