ATI Scheduler following Win10 upgrade to 1709
I upgraded my Windows 10 PC to version 1709 on Dec 11 and a laptop a few days later. These were both "update in place" upgrades. Since then (except once!) the ATI Scheduler has been failing. This is ATI 2018 Build 10410.
When it is time for a scheduled backup the following error is logged in the Windows log file:
Log Name: Application
Source: Acronis Scheduler
Date: 12/18/2017 10:00:01 AM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: PUGET-116877\Patrick
Computer: Puget-116877
Description:
Scheduler failed to run task >> "" with GUID '4333E2CC-3C0C-4F52-90BF-08BCEEAE8140'
because of error 5> (Access is denied.).
When Windows is rebooted the following error is logged:
Log Name: Application
Source: Acronis Scheduler
Date: 12/11/2017 8:55:12 PM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: PUGET-116877\Patrick
Computer: Puget-116877
Description:
Scheduler failed to run task >> "" with GUID '1E075F4C-6EE2-4D1D-BEA3-532FDE79BBF6'
because of error 87> (Scheduler has received a request with an invalid parameter.).
The backups run fine when manually started.
I know that "update in place" upgrades can mess up systems but these seemed pretty clean, and ATI has not choked on any of mine in the past. Does this sound like a familiar problem? I couldn't find anything on the web resembling this.
Earlier I said this error has happened "except once". That one successful run was the first scheduled backup following the Windows upgrade.
The "Access denied" error makes me wonder if authorities got messed up. Would reinstalling ATI possibly help?


- Accedi per poter commentare

Steve, one of those GUIDs, and another that I had missed in the events, are the script names for the scheduled ATI backups. I could not find the script invoked following a boot of Windows. Maybe it gets dynamically built and then deleted.
I've seen several reports of ATI errors similar to this. One solution involved reinstalling the ATI scheduler but that was from 2010 and almost certainly obsolete.
I'd be tempted to do a "rebuild" reinstall of ATI but the fact that this error is happening on 2 computers makes me think it is not a glitch that a rebuild will fix.
I have a 3rd computer that has no backups scheduled. Maybe I'll see if it can successfully run a scheduled backup.
- Accedi per poter commentare

Patrick, have you tried doing a 'task zap' using the Scheduler Manager to clear out all / any scheduled tasks then reconfiguring those schedules in the tasks?
- Accedi per poter commentare

Thanks Steve, I'll give that a try.
I decided it wouldn't hurt anything to try a rebuild install and was very surprised to see it do an update instead so I wonder if something went wrong in my install of 10410. ATI claimed it was on 10410 but I would have expected a repair if all was well.
I've got a scheduled restore to kick off in a few minutes. If it still fails I'll try the Task Zap.
- Accedi per poter commentare

The error 87 happened again (when I rebooted after the reinstall of ATI) but the scheduled backup started (and completed) with no problem. And I see that the error 87 happens during shutdown rather than reboot, and it has already been discussed here:
https://forum.acronis.com/forum/acronis-true-image-2018-forum/acronis-s…
Innocuous. I can ignore it.
- Accedi per poter commentare

I tried the update/repair on the laptop and it showed "Repair" (as expected) rather than "update" (as was shown on my PC). I have not had access to the laptop since the repair and following reboot but I don't see a new backup file on the target (a NAS drive) so I assume the scheduled backup did not happen.
- Accedi per poter commentare

I have similar issue (same error). From what I can tell, there is absolutely nothing wrong with the backup/set-up itself, it's only the scheduled tasks... after running manually once after set up, they usually work for 1 or 2 days/executions, then fail with this error.
I have:
- reinstalled;
- removed all tasks and created from scratch again
- provided logs files and reports to support team
No resolution in sight.
It "appears" (given the error message) that the scheduler at some point "forgets" the credentials use for the back-up and simply starts failing... it really shouldn't be that hard to resolve this... or at least for someone from Acronis to actually troubleshoot based on their code base!
- Accedi per poter commentare

Kyle, welcome to these User Forums.
If this is a reproduceable issue for you, then I would suggest opening a Support Case direct with Acronis to have them investigate it further.
- Accedi per poter commentare

- Accedi per poter commentare