New NAS: Sync runs ok in FFS, fails when scheduled

[terbos]

I just got a new NAS that dropped in at the same name and IP as the old NAS. The only notable thing that changed was the new NAS forced me to use a different password for my user account. This password does not match my Windows password.

Now, a daily sync job that has been working fine for years is broken. If I open the FFS gui, the job runs fine, but when the exact same FFS batch file is run from the Windows scheduler, it fails with permission errors on the NAS. This is true whether it runs at the scheduled time or if I force a manual run in the scheduler.

The job is mirroring files from Win10 to a Synology NAS. I'm using UNC syntax for the network paths.

I have another Win10 machine on my network that is doing basically the same thing and it works fine, including a mis-matched password. So it's just this one machine that's having a problem.

I'm looking for suggestions on where to look or how to get more information to diagnose it.

Thanks

[therube]

Out of my league, but...

Task Scheduler give you a log?
What does that say?

Perhaps something like, https://social.technet.microsoft.com/Forums/en-US/6b32e531-4900-4742-b652-0d05fd4668a4/do-we-still-need-to-update-password-for-task-scheduler-in-windows?forum=ws2016 ?

[terbos]

Thanks for the reply, but that's not it. The scheduled task is running, but FFS is logging permission errors when it tries to access the NAS.

[terbos]

These two logs were captured minutes apart. The only difference is that the success was launched from the GUI and the failure was launched from the Windows Task Scheduler. The system had not been rebooted and the file shares were accessible the whole time.

https://1drv.ms/u/s!AkpuZvfh0DaAg8R0AYhWxMnLBcb4hA?e=jnfgNC
https://1drv.ms/u/s!AkpuZvfh0DaAg8R1ivCKBMYW7U7XBA?e=rk4ZsM

[Plerry]

Perhaps this is also relevant here.

[xCSxXenon]

Have you opened credential manager in Windows and removed the possibly stale entries?

[terbos]

Thanks for the tip @xCSxXenon. It looks like I had multiple stale credentials stacked up on that server/account. Removing them all and recreating a new one seems to have fixed the problem. At least it worked by running the scheduled task manually. I'll see if it runs on the schedule overnight, but it'll probably work.