FFS stop working in Windows Server 2012 64 bit

Get help for specific problems
Posts: 4
Joined: 14 Dec 2021

infobfs

Hi.

I've been using FFS for some months in Windows Server 2012 64 bit.
I have a scheduled task running twice a day.
Everything worked just fine till 20-11-2021.
I don't remember if i did a FFS update or not, but the fact is that Windows Task Scheduler (WTS) shows a 0x2 code and the FFS batch isn't executed.
What happened?

If I run the .ffs_batch file manually everything works fine.
If it's started from WTS doesn't work, and show a 0x2 code.

I have two processes running:
"C:\Program Files\FreeFileSync\FreeFileSync.exe" "E:\ffsfiles\myfile.ffs_batch"
"C:\Program Files\FreeFileSync\Bin\FreeFileSync_x64.exe" "E:\ffsfiles\myfile.ffs_batch"

Can anyone help me, please?
User avatar
Posts: 4867
Joined: 11 Jun 2019

xCSxXenon

What if you just recreate the tasks?
Are you running them as SYSTEM?
User avatar
Posts: 2946
Joined: 22 Aug 2012

Plerry

The WTS 0x2 code seems related to "Access denied" or "Cannot find the specified file".
• If it worked before: instead of an FFS update, a Windows update is probably a more likely cause, and may have changed some "security" or other settings.
Some hints:
• As what user have you defined WTS to run the FFS task?
• Is drive E: defined for that user, and if so, does it point to the expected/assumed location (drive assignment is user specific)?
• Does that user have (at least) read access to that location?
Perhaps also look here.
Posts: 4
Joined: 14 Dec 2021

infobfs

What if you just recreate the tasks?
Are you running them as SYSTEM? xCSxXenon, 14 Dec 2021, 16:32
Already recreate and then I get a 0x80070002 error code

Running as DOMAIN\Administrator
Posts: 4
Joined: 14 Dec 2021

infobfs

• If it worked before: instead of an FFS update, a Windows update is probably a more likely cause, and may have changed some "security" or other settings. Plerry, 14 Dec 2021, 16:32
That's a possibility indeed...
• As what user have you defined WTS to run the FFS task? Plerry, 14 Dec 2021, 16:32
DOMAIN\Administrator
• Is drive E: defined for that user, and if so, does it point to the expected/assumed location (drive assignment is user specific)?
• Does that user have (at least) read access to that location? Plerry, 14 Dec 2021, 16:32
Drive E: is a local disk
And DOMAIN\Administrator as Full Control over it
Perhaps also look here. Plerry, 14 Dec 2021, 16:32
I'll take a look...
Posts: 4
Joined: 14 Dec 2021

infobfs

Perhaps also look here. Plerry, 14 Dec 2021, 16:32
Run with highest privileges already checked