I'm new to FreeFileSync, having had to replace synctoy due to the 255 char file limit.
I wanted to get this running as a scheduled task, so I followed the help and setup RealTimeSync.exe to run at startup. Unfortunately this only seemed to work once and then the process had to be terminated and restarted. I noticed that an instance of FreeFileSync.exe was still running as well.
Each time I restarted the sync, the FreeFileSync.exe was loaded (expected) but did not terminate.
I then setup a scheduled task to run FreeFileSync.exe every 5 minutes instead. Again this would leave an instance of FreeFileSync.exe running after each run. I've had to configure the task to terminate any previous jobs when it runs to keep the sync going. The sync does work (logging enabled and files being generated), but the machine running it constantly has instances of FreeFileSync.exe running.
Machine is Windows 8 syncing to a folder on Windows XP. Both are domain joined, scheduled task is running as System.
Anyone have any issues as to why this instance is remaining in memory?
Thanks
Tim
FreeFileSync.exe not terminating after running as scheduled task
- Posts: 1
- Joined: 10 Dec 2012
- Posts: 3
- Joined: 2 Jul 2013
I am seeing the same issue on Win7 Pro 32-bit machine. FreeFileSync.exe and FreeFileSync_Win32.exe processes are not terminating after scheduled tasks have completed. I end up with multiple instances of these processes.
-
- Site Admin
- Posts: 7212
- Joined: 9 Dec 2007
This is probably related to FFS showing some kind of modal dialog in the background. See the help file for details on how to avoid this.
- Posts: 3
- Joined: 2 Jul 2013
The modal dialog was apparently the problem. I didn't have the 'Close progress dialog' option set for 'On completion'.
I originally had the scheduled task set up to 'Run whether user is logged on or not'. But this made the progress window invisible (so I never saw it and could never close it manually). I changed the scheduled task to 'Run only when user is logged on' and now I see the progress window. When it finishes and I dismiss the progress window, the processes are terminated.
So it might be good to note in the help docs that if you set up a scheduled task to 'Run whether user is logged on or not', it is crucial to set the 'Close progress dialog' option also (and that the progress window will be invisible). Otherwise you stuck with open processes.
I originally had the scheduled task set up to 'Run whether user is logged on or not'. But this made the progress window invisible (so I never saw it and could never close it manually). I changed the scheduled task to 'Run only when user is logged on' and now I see the progress window. When it finishes and I dismiss the progress window, the processes are terminated.
So it might be good to note in the help docs that if you set up a scheduled task to 'Run whether user is logged on or not', it is crucial to set the 'Close progress dialog' option also (and that the progress window will be invisible). Otherwise you stuck with open processes.
