Acronis TI 2020: Scheduler2 has stopped
I am (still) running Windows 7 Home Premium (64 bits), and since I added another 16 GB of RAM, I get this message, each time I boot or reboot my PC. My PC is multibooting Win7, Win10Pro and Linux Mint 19.2. (Each on their own SSD or HD).
I have never had this problem before.
I have already excluded the .exe-files, and the relevant folders for MS Security Essentials, but to no avail.
I noticed some issues with Scheduler2 on here with 32-bit versions of Windows - in 2013!!
What is going on here? Is it a Windows issue? When I run Windows Troubleshooter, it tells me there are too many services at startup, but, what the heck? I did not add any services, recently, that I am aware of.
I have stopped some of these services from starting, but the remaining ones are essential to me, or to running the PC (erring on the side of caution, here; if the service is native to Windows, I assume it SHOULD run).
I want to make sure Win7 is running smoothly, before I try to upgrade it to Win10; Win7 holds most of my programs and settings, and I noticed some settings are quite tough to replicate in a fresh install of Win10.
To be sure: I have tested my RAM, but see no issues there; all the sticks are similar (11-11-11).


- Log in to post comments

Thanks for your response, Steve.
I have temporarely removed the extra RAM, but that did not change much. I did read about Win7 32-bits, that adding RAM above the 4 GB limit could mean that the amount of effective and available RAM might be less than 4 GB.
I am running the latest build of ATI 2020; I always update, whenever a new update becomes available.
I may still try that 'Repair Install', but I am actually wondering now, if it is all that important for me: all my backups are one-off, and span the whole drive. I validate them at the moment I create them, and don't do incremental backups (it once failed me in the past, and that cured me for good). I have been able to create backups in the last couple of days, so Scheduler either restarts on its own, or it is not relevant in my case. And I simply hate it, when some process starts up by itself to renew a validation, or to update a backup - it's as bad as Windows 10 forcing an update on me, just when I want to do something else. And I do not use the infamous 'Cloud', or use the 'Sync' function; I don't have a 'smart'phone or a tablet.
I just rebooted my PC, and the notice 'Scheduler Service is stopped' appeared, as usual, but it went off after a couple of minutes, and just now, when I clicked on the icon in the taskbar, it shows me a report about successful backups I recently created, and recent changes I made/allowed to Acronis Active Protection. So it would seem as if ATI is working OK for me. Well, apart from the fact, that it seems to take ages to load the User settings, but that issue has bothered me since I upgraded to ATI 2020....
....and now, the website goes all clunky, lol....reporting an 'unexpected error' when I click on 'save'
- Log in to post comments

I occasionally get the "Scheduler2 has stopped" shortly after booting my Win 10 computers, but the task is always running when I check. I don't know if it has been restarted or if the message was in error. It's a bit disconcerting to see the message, but I can see no damage done. (Next time I see it I'll look in the Windows Event Logs to see if anything is logged.)
- Log in to post comments

This is probably the action set on the Scheduler 2 Recovery tab page.
As shown above, the service is attempted to be restarted for the first & second failures, and could be set to do the same for subsequent failures/
- Log in to post comments

Thanks Steve. I'd never paid attention to recovery options. I guess I should now start paying attention to those Scheduler failures. I've never seen 2 in a row so I assume it's a timing issue of some sort.
- Log in to post comments

It might be worth setting the service to Automatic (Delayed start) to see if that gets rid of the error.
- Log in to post comments

BrunoC wrote:It might be worth setting the service to Automatic (Delayed start) to see if that gets rid of the error.
Actually, that may be the cause of the problem. I have it set for Automatic (Delayed start).
I just restarted a PC a few minutes ago and got the error. Judging from the Schedul2 logs, during restart processing the previous execution of Scheduler2 ended at 12/23/2019 6:56:47 PM. The current execution started at 12/23/2019 6:59:29 PM. From the Ti_monitor log I see:
12/23/2019 6:57:48 PM: -08:00 8948 I00000000: Monitor started. Version: 23.5.1.17750.
12/23/2019 6:57:48 PM: -08:00 8948 I00000000: Load qt resources
12/23/2019 6:57:49 PM: -08:00 8948 I00000000: GetDisplayInfo succeeded: DPI: 96, scaling: 100%. Monitors: Resolution: 1680x1050, work area: 1680x1020, physical DPI: 76.
12/23/2019 6:57:49 PM: -08:00 8948 I00000000: EnableHiDpiScaling - use system scaling.
12/23/2019 6:57:49 PM: -08:00 8948 I00000000: Init GA events
12/23/2019 6:57:49 PM: -08:00 8948 I00000000: DeviceAttachChecker was created
12/23/2019 6:57:49 PM: -08:00 8948 I00000000: Creating ransomware check operation
12/23/2019 6:57:49 PM: -08:00 9632 I00000000: DeviceAttachChecker. Operation started
12/23/2019 6:57:49 PM: -08:00 9632 E00000000: DeviceAttachChecker. Failed to connect to scheduler: ConnectLocal failed: Error 0x901fa: RPC client error.
Lots of detailed error records follow, but it really doesn't matter. The monitor checked for the Scheduler 101 seconds before the Scheduler started.
The error message about the stopped Scheduler is accurate but totally irrelevant. The message should be ignored if the Scheduler is actually running.
- Log in to post comments

The Scheduler 2 service shouldn't be set to Automatic (Delayed) under normal circumstances.
- Log in to post comments

Thanks, Steve, Patrick and Bruno,
I have not been able to find the panel Steve showed, but, judging from what you guys wrote I think it's best to leave it well enough alone. I have recently installed ATI 2020 on my clean Win10Pro SSD, and there, I don't see any reports about Scheduler.
Just got to remember NOT to open ATI right after booting Windows, but then: rushing to create a backup or to restore a disk is seldom a good idea....have a cuppa first...
- Log in to post comments

Lex Noyb wrote:Just got to remember NOT to open ATI right after booting Windows, but then: rushing to create a backup or to restore a disk is seldom a good idea....have a cuppa first...
I don't think opening the ATI GUI has any effect on this issue. The monitor task and the scheduler service start in the background.
Steve Smith wrote:The Scheduler 2 service shouldn't be set to Automatic (Delayed) under normal circumstances.
Hmm. I'm not sure why I have that. It's only on one computer - one running ATI 2019. I must have been trying to diagnose something and forgot to set it back to Automatic. I'll set it back and see if I still get the message.
- Log in to post comments