From my log:
FreeFileSync - Batch execution - 12/01/2012
-------------------------------------------
Synchronization completed with errors!
[12:45:00 AM] Start
[12:45:27 AM] Error: Directory does not exist:
"\\Linky\Volume_1\Backups\Sammy_Home\"
You can ignore this error to consider the directory as empty.
[12:45:51 AM] Info: Processing folder pair:
Left: "D:\Home\"
Right: "\\Linky\Volume_1\Backups\Sammy_Home\"
[12:45:51 AM] Info: Creating folder "\\Linky\Volume_1\Backups\Sammy_Home\andrew.m"
[12:45:51 AM] Info: Creating file "\\Linky\Volume_1\Backups\Sammy_Home\andrew.m\Bullseye referal Form.lnk"
[12:45:52 AM] Error: Error moving file:
"\\Linky\Volume_1\Backups\Sammy_Home\andrew.m\Bullseye referal Form.lnk.ffs_tmp" ->
"\\Linky\Volume_1\Backups\Sammy_Home\andrew.m\Bullseye referal Form.lnk"
Windows Error Code 183: Cannot create a file when that file already exists.
(Then I get thousands of these same errors)
The directory does exist, and this doesn't happen every time (this job
runs every night). The remote \\Linky\ fileshare is a D-Link ShareCentre NAS.
I'm using FFS 4.6. The local machine is a Windows 2003 Server.
Any ideas why this is happening? I'm going to try mapping the share to a
windows drive letter and see if that helps.
Regards
Gavin
Directory does not exist (when it does!)
- Posts: 4
- Joined: 11 Jan 2012
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
FFS automatically tries to logon to network shares before checking directory
existence. Maybe this is somehow related to a small delay after logon and
before directory is reported as existing by the os.
Does the same problem happen if you sync via gui and/or if you press "retry" a
couple of times?
existence. Maybe this is somehow related to a small delay after logon and
before directory is reported as existing by the os.
Does the same problem happen if you sync via gui and/or if you press "retry" a
couple of times?
- Posts: 4
- Joined: 11 Jan 2012
It has never happened using the GUI, but I don't use the GUI often.
It has worked fine since I changed to using mapped drives, but its only been a
few days, so I will let you know if it happens again.
It has worked fine since I changed to using mapped drives, but its only been a
few days, so I will let you know if it happens again.
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
Mapped drives are yet another layer on top of UNC paths, so generally I would
expect latter to create less problems. Anyway, if you face this problem again,
try to find out what triggers it and ideally how it can be reproduced.
expect latter to create less problems. Anyway, if you face this problem again,
try to find out what triggers it and ideally how it can be reproduced.
- Posts: 3
- Joined: 10 Nov 2010
I have a similar issue where Freefilesync doesn't report files and folders to
be missing on either side, for example it reports 2 missing folders on the
right side, when I can check both folders and plainly see that there is 3
folders missing etc.
This has now caused me to stop using Freefilesync, I am very dependent on this
software to sync both sides 100% correctly, as other people depend on me
synching my files correctly.
I'm using 5.0.
be missing on either side, for example it reports 2 missing folders on the
right side, when I can check both folders and plainly see that there is 3
folders missing etc.
This has now caused me to stop using Freefilesync, I am very dependent on this
software to sync both sides 100% correctly, as other people depend on me
synching my files correctly.
I'm using 5.0.
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
> I have a similar issue where Freefilesync
This seems to be a different problem than the one by the original poster.
Please open a new bug tracker item, and let's analyze it.
This seems to be a different problem than the one by the original poster.
Please open a new bug tracker item, and let's analyze it.