Error Code 3 - path not found

[Squashed]

I'm getting the following error:-

Error Cannot create directory "X:\".
Error Code 3: The system cannot find the path specified. (CreateDirectory)

X:\ is a mapped network drive to a NAS share to hold my version history. I can see the drive in Windows Explorer and write to it.

I have specified X:\ on the Synchronization Settings > Versioning section with a path like X:\Users\UserName\My Photos. I have a dozen or so pairs of source/target mirrors, each with its own X:\ path set for Versioning. The targets are all on mapped drive W:\.

The error only arises with changed/deleted files where FFS is trying to update or move a file from W:\ to X:\.

[Zenju]

Which version of FreeFileSync are you using? I'd like to analyze the file access pattern, maybe there's something for FreeFileSync to improve. Set up Process Monitor and record a trace when you click on "retry":
https://freefilesync.org/faq.php#trace

[Squashed]

I sent you a pml file yesterday. Hope it helps. I'm using version 7.8. Thanks.

[Zenju]

The PML file doesn't contain the error from above, but only a short part saving some "*_Organizer_V1.PDF" file.

[Squashed]

Tried upgrading to version 8.0. Still getting same error. Don't know why it's not logged in pml or how to get more error info. I suspect the reason it showed the pdf files were saved is that they were new files, so nothing needed to be moved into version history on the server.

I'm reluctantly going to try using SFTP instead, which I didn't want to do because setting up the targets and versioning for 12 or so folder pairs in FFS with SFTP is not neat and easy to see as using a simple drive letter.

A suggestion to manage this would be to globally assign the server connection strings in FFS to symbols (just like Map a Network Drive) and then use those symbols in defining the target/versioning folders.

[Zenju]

Did you check if you're accidentally running the FreeFileSync process under a different user? Maybe you're running it as administrator? Mapped network drives can only be seen by the user who created them.

[Squashed]

I switched all the references to X:\ drive to use SFTP instead and now it runs fine in batch and interactive. I still kept the target folders using mapped drive W:\ and FFS works with that OK. It's just the X:\ that I used on the version history folders that I switched. So it can't be anything to so with users. I had checked that anyway on the batch job.

[jmpr]

I have the same problem. FFS doens't "see" the network drives. I haven't changed anything. Batch files that have always run for years now can't sync. If I try to create a new job, I can't select network drives.

I'm using the last version in Windows 10 pro 64.

[bnfoat]

I am getting a similar error running version 8.1 on a Windows 7 Pro 32bit. Error Code 3. and the file does not sync
[8:59:02 PM] Info: Synchronizing folder pair: [Mirror ->]
C:\Users\Owner\Documents
\\backupserver\download\HPm7757cBU\Owner\Documents
[8:59:02 PM] Info: Updating file "\\backupserver\download\HPm7757cBU\Owner\Documents\FreeFileSync.doc"
[8:59:02 PM] Error: Cannot create directory "W:\".
Error Code 3: The system cannot find the path specified. (CreateDirectory)