Sorry for a double-post - I'm still finding my way around here and didn't realize there's a specific separate "Help" forum. As it turns out, my original post was in "Open Discussion."
I've just started trying to use FFS last night, synching two music folders within the Music libraries of two different computers on the network.
When I started, I ran into the documented "can't write" problem, read up here, and ignored it - and it continued on just fine. (Note: there's a link in that thread to some instructions on advanced settings to disable the test entirely - that link is broken.)
Unfortunately, the remote computer shut down before the synch completed. It's back on again, and the files are accessible, but now the synch won't work at all due to write access problems - ignoring doesn't help. I didn't shut down FFS during that time; it reported a problem and I just left it until the remote computer was back on again and then said "retry" - which didn't work. I tried shutting down and restarting FFS; no help.
It's very much like the already-documented write problem, but ignoring doesn't work; it just ends the synch "with errors."
Any help? Is there some sort of hidden file over there that I need to remove or something?
Directory write issue (not the one already documented)
- Posts: 13
- Joined: 21 Apr 2015
-
- Site Admin
- Posts: 7282
- Joined: 9 Dec 2007
Not quite sure which problem you are referring to. Maybe you could elaborate a bit more?
- Posts: 13
- Joined: 21 Apr 2015
OK. There's a documented issue where, when you try to sync, you get an error "can't write sync file" or something similar. The instructions there are either to say "Ignore" and check "do this every time" (which I did) or change some advanced setting (and there's a link that's broken; I couldn't follow that). The link to this discussion is: viewtopic.php?t=2163
This happened when I first started the sync, and I ignored, and things went fine - until the computer on the other end (not the one running FFS, but the one I'm synching with - I'll call it the remote machine) shut down, interrupting the sync.
On the local machine (running FFS), a dialog opened saying it couldn't get to the remote computer (as a result of the shutdown). I left that dialog open, untouched, until the remote machine was back online (and I could see all the files and such in Windows). I then hit "retry" on the local machine, and it came with that same "can't write sync file" thing as before, only now, when I hit "ignore," it stops the sync. I've attached a screenshot of the dialog that resulted.
So, unlike the first time, "ignore" is no longer a successful strategy. I don't know if this is a variant on the original "can't write" thing where the "ignore" does work, or if this is a completely different thing that just looks like it. Bottom line is that I can no longer sync, and it provides no information as to what the problem is (in a form that I could do something about).
Both machines are Windows 7 64 bit. Connecting via homegroup. Synching folders in the Music library.
Is that enough to clarify the problem? If not, let me know what other details would be useful.
Thanks.
This happened when I first started the sync, and I ignored, and things went fine - until the computer on the other end (not the one running FFS, but the one I'm synching with - I'll call it the remote machine) shut down, interrupting the sync.
On the local machine (running FFS), a dialog opened saying it couldn't get to the remote computer (as a result of the shutdown). I left that dialog open, untouched, until the remote machine was back online (and I could see all the files and such in Windows). I then hit "retry" on the local machine, and it came with that same "can't write sync file" thing as before, only now, when I hit "ignore," it stops the sync. I've attached a screenshot of the dialog that resulted.
So, unlike the first time, "ignore" is no longer a successful strategy. I don't know if this is a variant on the original "can't write" thing where the "ignore" does work, or if this is a completely different thing that just looks like it. Bottom line is that I can no longer sync, and it provides no information as to what the problem is (in a form that I could do something about).
Both machines are Windows 7 64 bit. Connecting via homegroup. Synching folders in the Music library.
Is that enough to clarify the problem? If not, let me know what other details would be useful.
Thanks.
- Attachments
-
- FFS screenshot.png (43.46 KiB) Viewed 397 times
-
- Site Admin
- Posts: 7282
- Joined: 9 Dec 2007
Issues like "access denied" have to be solved outside of FreeFileSync. You have to make sure that FreeFileSync has full write permissions on the folders that are synced. How this is done in practice depends: e.g. for NTFS volumes there are NTFS permissions that need to grant the corresponding rights to the specific user that is syncing. For network storages this can be usually set up via a specific web interface, etc...
- Posts: 13
- Joined: 21 Apr 2015
But it was working until it was interrupted. So something changed from the start of the sync to the attempt to restart. That's why it seems that FFS would have had some impact on what changed.
At this point, if there's no solution, I simply have to conclude that FFS isn't useful for the regular person, that it's a brittle program that can't recover from being interrupted. (And I'm actually much more tech-savvy than you're average person, but I'm not an IT guy. And I don't want to have to be.)
At this point, if there's no solution, I simply have to conclude that FFS isn't useful for the regular person, that it's a brittle program that can't recover from being interrupted. (And I'm actually much more tech-savvy than you're average person, but I'm not an IT guy. And I don't want to have to be.)
