I was using FFS without any glitch to mirror data from my desktop on my laptop
until the recent updates. Now, after every sync I get this error: Error
setting directory lock:..........directory path\sync.ffs_lock. Windows error
code 5: Access is denied.
Why is this happening. What can i do to solve this?
Error setting directory lock
- Posts: 17
- Joined: 9 May 2011
-
- Site Admin
- Posts: 7058
- Joined: 9 Dec 2007
I assume you successfully used v3.21 and the error is new for v4.0?
I changed the file access setting from write-only to read-write, which
according to MS documentation is a more compatible setting and avoids certain
"access denied" errors over a network.
Since this is the only change, I suspect this to have triggered another error.
Under the assumption that MS's recommendation is correct, the only option is
to change one of the other parameters, so I enlarged share permissions from
read-only to read/write/delete.
Here's the new 32-bit exe for testing (place in subfolder "bin")
[404, Invalid URL: http://ifile.it/zf2k7mh/FreeFileSync_Win32.exe]
Solved?
I changed the file access setting from write-only to read-write, which
according to MS documentation is a more compatible setting and avoids certain
"access denied" errors over a network.
Since this is the only change, I suspect this to have triggered another error.
Under the assumption that MS's recommendation is correct, the only option is
to change one of the other parameters, so I enlarged share permissions from
read-only to read/write/delete.
Here's the new 32-bit exe for testing (place in subfolder "bin")
[404, Invalid URL: http://ifile.it/zf2k7mh/FreeFileSync_Win32.exe]
Solved?
- Posts: 17
- Joined: 9 May 2011
Thanks for the reply!
I have already set the permission to read & write. Despite this the program is
occurring.
I copied the specified file to the bin sub-folder but the problem persisted.
But so far the syncing is okay despite the error report! I would choose to
ignore this error so long as my files sync properly.
FFS is a marvelous software. Has made my life much easier. Loving it! I hope
the next update fixes this issue...
I have already set the permission to read & write. Despite this the program is
occurring.
I copied the specified file to the bin sub-folder but the problem persisted.
But so far the syncing is okay despite the error report! I would choose to
ignore this error so long as my files sync properly.
FFS is a marvelous software. Has made my life much easier. Loving it! I hope
the next update fixes this issue...
-
- Site Admin
- Posts: 7058
- Joined: 9 Dec 2007
> I have already set the permission to read & write. Despite this the program
is occurring.
> I copied the specified file to the bin sub-folder but the problem persisted.
> But so far the syncing is okay despite the error report! I would choose to
ignore this error so long as my files sync properly.
The locking file is only required if there is chance that multiple instances
of FFS are simultaineously accessing the same folder like in a distributes
network. In other cases, the error can be ignored. But still, there shouldn't
be any error, since the locking file ist just "a simple file", there is no
reason why writing it should fail.
> FFS is a marvelous software. Has made my life much easier. Loving it! I hope
the next update fixes this issue...
Unfortunately I'm not able to reproduce this problem, in my tests everything
runs fine. In case you find out under what circumstances this happens, I might
be able to reproduce it, which is almost equivalent to being fixed.
is occurring.
> I copied the specified file to the bin sub-folder but the problem persisted.
> But so far the syncing is okay despite the error report! I would choose to
ignore this error so long as my files sync properly.
The locking file is only required if there is chance that multiple instances
of FFS are simultaineously accessing the same folder like in a distributes
network. In other cases, the error can be ignored. But still, there shouldn't
be any error, since the locking file ist just "a simple file", there is no
reason why writing it should fail.
> FFS is a marvelous software. Has made my life much easier. Loving it! I hope
the next update fixes this issue...
Unfortunately I'm not able to reproduce this problem, in my tests everything
runs fine. In case you find out under what circumstances this happens, I might
be able to reproduce it, which is almost equivalent to being fixed.
