I've created a sync job in FFS GUI having mapped Y: to one remote shared folder (Source) on one NAS drive and Q: to one remote folder on a different NAS drive.
When I run a manual compare and sync the files are replicated fine. But when I generate it into a batch file I get the following error log (running as same user)
==========================================================================
_____________________________________________________________
|11/08/2014 - BatchRun: Synchronization completed with errors
|
| Items processed: 0
| Items remaining: 5,731 (13.5 GB)
| Total time: 00:24:31
|____________________________________________________________
[22:00:04] Info: Starting comparison
[22:00:07] Error: Cannot find the following folders:
Q:\
You can ignore this error to consider each folder as empty. The folders then will be created automatically during synchronization.
[22:24:34] Info: Synchronizing folder pair:
Y:\
Q:\
[22:24:35] Error: Cannot create directory "Q:\".
Error Code 3: The system cannot find the path specified. (CreateDirectory)
[22:24:36] Error: Synchronization completed with errors
===========================================================================================
I've changed it to sync just one folder on the drive and I get the same error in this log
===========================================================================================
_______________________________________________________________________
|12/08/2014 - President.BatchRun: Synchronization completed with errors
|
| Items processed: 0
| Items remaining: 46 (0 bytes)
| Total time: 00:01:07
|______________________________________________________________________
[17:10:55] Info: Starting comparison
[17:10:56] Error: Cannot find the following folders:
Q:\President\
You can ignore this error to consider each folder as empty. The folders then will be created automatically during synchronization.
[17:12:02] Info: Synchronizing folder pair:
Y:\President\
Q:\President\
[17:12:02] Error: Cannot create directory "Q:\".
Error Code 3: The system cannot find the path specified. (CreateDirectory)
[17:12:03] Error: Synchronization completed with errors
===========================================================================================
Any ideas where I am going wrong?
Error Code 3 when running as a Batch File
- Posts: 1
- Joined: 12 Aug 2014
- Site Admin
- Posts: 7212
- Joined: 9 Dec 2007
This seems to be a recurring issue discussed here but I didn't find the best thread quickly, maybe this one:
viewtopic.php?t=1178&p=5159#p5159
General issue: mapped network shares are only visible to your user account, but not for other accounts or the admin account. So you need to make sure to setup task scheduler to run under your account - or don't use mapped shares, but UNC syntax instead.
viewtopic.php?t=1178&p=5159#p5159
General issue: mapped network shares are only visible to your user account, but not for other accounts or the admin account. So you need to make sure to setup task scheduler to run under your account - or don't use mapped shares, but UNC syntax instead.
- Posts: 1
- Joined: 2 Jan 2015
What if you're running into this exact error... but it happens even when you are already using the full UNC path and you're not even using task scheduler yet? I set up an OpenMediaVault NAS for some family members so their Windows 8.1 laptop could sync items over as a backup. I'm only running the sync through the FreeFileSync GUI right now as I wanted to see it succeed first, then set it up through task scheduler afterwards and ensure that it successfully copies over newly created items.
About half of the time it will throw this error, but other times it won't. Due to this I haven't even explored task scheduler as I want to ensure it works predictably first. The pairing is simple. It's a mirror pair set so it deletes items on the destination that don't exist on the source. Source path is C:/Users/frank, destination is \\192.168.1.20\frank.
Frank has the exact same login credentials (username + password) on the local Windows 8.1 machine as he does on the NAS to log in.
Has anybody else seen this despite not using mapped network drives and whatnot as I described above?
About half of the time it will throw this error, but other times it won't. Due to this I haven't even explored task scheduler as I want to ensure it works predictably first. The pairing is simple. It's a mirror pair set so it deletes items on the destination that don't exist on the source. Source path is C:/Users/frank, destination is \\192.168.1.20\frank.
Frank has the exact same login credentials (username + password) on the local Windows 8.1 machine as he does on the NAS to log in.
Has anybody else seen this despite not using mapped network drives and whatnot as I described above?