Help with Task Scheduler

[formy808]

I set up my .ffs_batch file and tested it by running from the command line. Everything works great. So then I created a Windows Task Scheduler entry (following the instructions in the docs) but for some reason it doesn't work. I get and error code 3 returned from FFS. Any idea what I'm doing wrong?

[blubb88]

No solution but another companion.

I have the same problem.
FFS worked till April 11'th. Eg. there was an Windows-Update? I don't know.
I only know that from that day FFS won't work with the TaskScheduler anymore and I don't know why.

If I run the FFS-Batch file from the FFS-GUI everything runs fine.
If I let ist run by the TaskScheduler the task will start, nothing happens and the task will end within 1 sec - without any error or remarkable information. Only Start and End.

I don't know what has changed and where to start to look for.

Has anyone any idea how to reactivate FFS with the Windows TaskScheduler again?
It's relatively urgent ;-)

[blubb88]

....add....

interesting:
If I run/start/dubbleclick the batch-file by myself FFS will do right.
If I let the TaskScheduler do that it won't do. :-(

I will now try with an without user logged in and see if there's any difference.

Edit 04-30-2017:

No difference.
TaskScheduler won't do it anymore! :-(
And I have no idea what prevents him to do it right as before April 11th.
In the log of the TaskScheduler everything looks fine.
The task starts in time and ends within the same second without any recognizable error massage. The log only shows the regular ending entry.

Anyone here hwo has an idea?

[Weffke]

Same issue, now using realtimesync instead.

I build a batch with this content that i run from the startup folder:

@echo off
start "realtimesync" "C:\Program Files\FreeFileSync\RealTimeSync.exe" "C:\D-to-B.ffs_batch"

Greets jeff

[blubb88]

My solution - Maybe adaptable for others:

As I found out the TaskScheduler (TS) can't access the customized netdrives (anymore?!). So if you let the task run with another user-account and/or without the user logged in you have to configure the paths to the file to be executed and the additional parameters with the absolute net-pathes ("\\servername\foldername\filename") and can not use the drive-letter of an configured net-drive (eg. "S:\folder\file").

In my case the entries "C:\programs\freefilesync\freefilesync.exe" with the parameters "S:\folder\file.ffs_batch" didn't work (as written above).
In that case the TS correctly starts FreeFileSync.exe but FFS won't find any batch-File due to TS won't find it, reacts with complications within the parameters and won't commit it (I estimate).
Worse in that case: Both programs run without any real error messages.
TS starts FFS (correctly). FFS does exactly what it's said (from TS), viz nothing and ends - amazed but correctly. So does TS afterwards.
Or did I overlook the purposeful message from TS or FFS? I didn't perceive any of the messages or logs as helpful.

As i changed the parameter entry to "\\server\folder\file.ffs_batch" everything runs fine (again).

So 'my' problem seems to be solved.

Strange in that case is that it worked the first way till April 11th.

Regards
Rainer

[formy808]

Hmm, that's interesting. I am also using the mapped drives rather than the \\server\share format. I will try that and report back.

[formy808]

Boom! That worked.