"sync.ffs_lock" cannot be written

Get help for specific problems
Posts: 2
Joined: 4 Nov 2025

anwin

Hello, I would like to use Freefilesync to back up from a Synology to a Server2019. I have been trying for several days, but I keep getting this error. How do I fix this, or where is the problem?
The task is running as an administrator and the network drives are permanently mapped. The two locations (non-profit organization) are connected via ipsec and Wireguard. Both sides are writable....
Errors and warnings:
23:20:28
The file "\\192.168.190.4\Education\sync.ffs_lock" cannot be written.
ERROR_NETNAME_DELETED: The specified network name is no longer available. [CreateFile]
23:20:28
The file "\\192.168.190.4\Athletics\sync.ffs_lock" cannot be written.
ERROR_NETNAME_DELETED: The specified network name is no longer available. [CreateFile]
Glossar
Posts: 1222
Joined: 8 May 2006

therube

Wireguard was mentioned, viewtopic.php?t=8943.
Maybe the workaround will work for you?

(Though per the Error message, "The specified network name is no longer available", it might be something different?)
Posts: 4908
Joined: 11 Jun 2019

xCSxXenon

If the network drives are mapped under your user session, FFS won't have access when ran as administrator since it is run under a different user, which does not have the network locations mapped. Shouldn't really matter, because those errors don't use mappings at all. Might need to run FFS as admin, use the browse button to get an admin File Explorer, and map or save credentials for the network locations that way.
Posts: 2
Joined: 4 Nov 2025

anwin

thanks all, Ticket ist off