[Bug Report] -deletions fail to sync when versioning is active

[dangerade]

When using the realtimesync deletions fail to sync in mirror mode when versioning is active. Renames, and new files are applied successfully. If same the same .ffs_batch file is run with freefilesync.exe deletions are successful and versions appear in the correct directory as desired.

The following popup error occurs when realtimesync.exe recognizes a deletion and attempts to move/create the versioned file in the target directory:

Cannot create directory "C:\Windows\system32\"Z:"
Error Code 123: The filename, directory name, or volume label syntax is incorrect. [CreateDirectory]

The target directory for versioning is a network drive mapped to Z:\ and the was entered using the "Browse" function in the dialogue box.

anyone have any idea what's going on?

[Zenju]

Which FFS version are you using? What exact path is used for versioning?

[dangerade]

I'm using ffs 8.9 donation edition build: Feb 13 2017 on Windows 7 x64
errors occur when running RTS through windows scheduler with the trigger "at log on"
The target is a network samba share mapped to the Z:\ in windows.

I found if I start rts manually with the same batch file used in scheduler it works with the versioning path Z:\z.deleted\adoc

But if I use that versioning path with scheduler I get the errors:

Cannot copy file
"C:\adoc\download\z.delet3d.bmp" to
"Z:\z.deleted\adoc\download\z.delet3d.bmp 2017-02-26 105035.bmp.ffs_tmp".

Error Code 3: The system cannot find the path specified. [CopyFileEx]

Cannot create directory "Z:\Sync\sync.logs".

Error Code 3: The system cannot find the path specified. [CreateDirectory]

I discovered a work around if I use the actual network path for versioning and log files e.g.
\\THENIGHTFORT\TheFrostFangs\z.deleted\adoc
everything seems to work as it should. I'm not sure why this should be the case. Maybe something with the order permissions are loaded or when the network file system is mounted by windows at login? But then why should the problem persist and not just error at the beginning? and the weird original error where it appeared it was adding C:\Windows\system32\ as a prefix to the target Z:\?

[Zenju]

Mapped drive letters are user-dependent and therefore often not available in the context of task scheduler. Workaround: explicit UNC syntax.