I've been experimenting with the free version of freefilesync. I don't use the real time sync version, so far. The deploy is on a small windows 2012r2 domain. It's being asked via batch to copy one file from A and one from from B to server C.
In the month or two I've had it running it's gone pretty well. That is until if completely fails. The first time was Aug 6, when I had 11.11 installed. It started generating empty dmp files to the desktop in some irregular pattern and failed to copy any files. When I caught on, a week later, I opened ffsync to see if it would run manually. It said 11.12 was available so I updated to that. From then on sync ran fine, or at least it did until Sept 3 when again it started generating empty dmp files to the desktop and stopped copying any files. Again the ffsync ui notified me that 11.13 was available, and after I updated, it's been sync'ing fine.
So far ffsync has been too unstable to rely on for production purposes. With only empty dmp files I'm not sure what the cause was. Does anyone have a clue? Is this common?
ffsync fails, empty dmp files, install update fixes it?
- Posts: 21
- Joined: 11 Sep 2021
- Posts: 2451
- Joined: 22 Aug 2012
I am not sure what you mean by dmp-files.
Or do you have crashes and are using the Process Explorer?
Note that if you have a single FFS sync from A to C and from B to C,
all resources involved in the sync need to be available, otherwise FFS will not sync.
So, if either A or B may be temporarily unavailable, it is better to have two separate FFS syncs:
1) A to C
2) B to C
I don't recognize FFS failing when a newer version has become available.
Or do you have crashes and are using the Process Explorer?
Note that if you have a single FFS sync from A to C and from B to C,
all resources involved in the sync need to be available, otherwise FFS will not sync.
So, if either A or B may be temporarily unavailable, it is better to have two separate FFS syncs:
1) A to C
2) B to C
I don't recognize FFS failing when a newer version has become available.
- Posts: 21
- Joined: 11 Sep 2021
Thanks for that input. I will split the batch into two: A C and B C
The dmp files are generated on the desktop, the full name is like
FreeFileSync_x64.exe 11.12 CrashDump 2021-09-03 130500.dmp
they are zero bytes - no content.
The dmp files are generated on the desktop, the full name is like
FreeFileSync_x64.exe 11.12 CrashDump 2021-09-03 130500.dmp
they are zero bytes - no content.
- Posts: 4056
- Joined: 11 Jun 2019
Empty dmp files are interesting. I would use a tool like RevoUninstaller to wipe FFS from the computer and install again
- Posts: 21
- Joined: 11 Sep 2021
Plerry, it seems likely that your tip has provided the solution. I've not had a recurrance of this issue since I split the syncs for pc A and pc B into distinct jobs. Thank you!