Scheduling stopped working


Author
Message
Gork
Gork
Guru
Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)
Group: Forum Members
Posts: 649, Visits: 2.7K
I noticed that.  But I seem to recall some other issues that occur because of this as well.  I just couldn't find the additional posts I was thinking of.  Or my old brain may have just made them up? heh
jewelr
jewelr
New Member
New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)
Group: Forum Members
Posts: 19, Visits: 113
Gork, Probably the latter BigGrin
anachromat
anachromat
New Member
New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)
Group: Forum Members
Posts: 13, Visits: 79
I noticed that my scheduled backups stopped running after "the big" Win 10 upgrade (to version 1607).  I don't believe I have anything substantial to add to this thread, though - really just noting that, whatever the problem really is, it apparently wasn't fixed before the retail Windows upgrade patch was released.  Deleting the current backup schedules and recreating them doesn't help.  Fiddling with the tasks directly in Task Scheduler can be made to work, but then Macrium Reflect loses track of them and doesn't create a log file.  Etc - all these things were reported before.
jewelr
jewelr
New Member
New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)New Member (34 reputation)
Group: Forum Members
Posts: 19, Visits: 113
anachromat - 7 August 2016 2:57 AM
I noticed that my scheduled backups stopped running after "the big" Win 10 upgrade (to version 1607).  I don't believe I have anything substantial to add to this thread, though - really just noting that, whatever the problem really is, it apparently wasn't fixed before the retail Windows upgrade patch was released.  Deleting the current backup schedules and recreating them doesn't help.  Fiddling with the tasks directly in Task Scheduler can be made to work, but then Macrium Reflect loses track of them and doesn't create a log file.  Etc - all these things were reported before.

I actual found a work around the other day. Seems to put Macrium schedules back to the way they are suppose to be (ie: logging the backups, getting the pop ups before the backup starts and functioning as expected). In task scheduler > go to the properties of the scheduled task you want to run and select "Run only when user is logged on". I am running the anniversary update of windows 10.
anachromat
anachromat
New Member
New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)
Group: Forum Members
Posts: 13, Visits: 79
jewelr - 7 August 2016 3:16 AM

I actual found a work around the other day. Seems to put Macrium schedules back to the way they are suppose to be (ie: logging the backups, getting the pop ups before the backup starts and functioning as expected). In task scheduler > go to the properties of the scheduled task you want to run and select "Run only when user is logged on". I am running the anniversary update of windows 10.

This didn't work for me, but I expect our setups are different:  a user with admin rights is essentially never logged in.  So if I set the task to run under an admin account, "Run only when user is logged in" never triggers.  But if I set the task to run under a non-admin user account, and it's logged in, the task triggers but fails to run.

Before the Windows Anniversary Update, when a backup task triggered a Windows elevation prompt popped up, asking for an admin acct/password.  That may be unbearable for most people Wink , but was fine for me.

LATER:  this seems to be working for me:  I left "Run whether user is logged on or not" alone, but changed (in Task Scheduler) the user account to an admin account (and gave Task Scheduler its password).  The jobs seem to run fine now, they still show up in the Reflect UI, and their history is in the Reflect log section.  I no longer get an elevation prompt, and, indeed, no longer get notifications of any kind - I can only tell the job is running by looking at the target directory in the backup destination disk, or by refreshing the Task Scheduler UI, or looking for the job in Task Manager.  Alas, if I edit a task _within_ Reflect, it appears to get reset to run under the non-admin account Reflect was launched under.

I can live with all that Satisfied

Edited 7 August 2016 5:34 AM by anachromat
Richard V.
Richard V.
Most Valuable Professional
Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)
Group: Forum Members
Posts: 2K, Visits: 8K
In fact, anachromat, I think you have provided more confirmation for what has been said about the problem in the other thread on this topic.  The Windows 10 "Anniversary Update" appears to have caused the Windows Task Scheduler 1.0 API to mishandle credentials that are required for scheduled tasks to run with elevated privileges.  Since Reflect uses that WTS 1.0 API to manage scheduling of its backup tasks, they fail to run as created and it seems you may have found another workaround for the problem.

Could you specify very precisely the exact steps that you took in the Task Scheduler, please.  When I tried doing the same as what I think you did I still got an error (0x800702E4 = Elevation required) under the Task Scheduler's Last Run Result column.

Regards, Richard V. ("Arvy")
https://forum.macrium.com/uploads/images/afc5d4fe-5d25-4e25-be94-185e.png

Edited 7 August 2016 7:29 AM by Arvy
BjornB
BjornB
New Member
New Member (20 reputation)New Member (20 reputation)New Member (20 reputation)New Member (20 reputation)New Member (20 reputation)New Member (20 reputation)New Member (20 reputation)New Member (20 reputation)New Member (20 reputation)New Member (20 reputation)
Group: Forum Members
Posts: 13, Visits: 75
For some years now I have loved mye Reflect dearly, it has been running almost without any issues on 12 computers, all automated backups. Then all of a sudden, when I was blessed with the Anniversary Update winver 1607, I was thrown out of Paradise. I have been reading all related posts in this forum since then, and apart from some very specific details by the specialists, I can make use of some information given by helpful people. I will know for sure when next weeks schedules start to run - whether I can see them or not or they will run at all remains to be seen.

This is my plea;
I really find it a bit unsatisfactory, to say the least, that Macrium has not bothered to provide their customers the infos badly needed. Not yet. It seems they leave it to each and every customer to struggle with this issue all by themselves. I very much rely on Reflect, I guess many more do the same, so please - help us out here!

Richard V.
Richard V.
Most Valuable Professional
Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)
Group: Forum Members
Posts: 2K, Visits: 8K
Completely agree, Bjorn.  The silence is unhelpful to say the least and quite unlike Macrium's very forthright and open behavior with various issues encountered in the past.  I'm sure they are working "behind the scenes", but in some ways (apart from Stephen's brief acknowledgement and this one in the other thread) the apparent lack of subsequent responsiveness here in this case is more disturbing than the task scheduling problem itself.  On the other hand, I don't actually use scheduling much myself, so maybe that's just my own reaction.


Regards, Richard V. ("Arvy")
https://forum.macrium.com/uploads/images/afc5d4fe-5d25-4e25-be94-185e.png

Edited 7 August 2016 7:09 PM by Arvy
anachromat
anachromat
New Member
New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)New Member (24 reputation)
Group: Forum Members
Posts: 13, Visits: 79
Arvy - 7 August 2016 6:27 AM
Could you specify very precisely the exact steps that you took in the Task Scheduler, please.  When I tried doing the same as what I think you did I still got an error (0x800702E4 = Elevation required) under the Task Scheduler's Last Run Result column.

Sure.  There are only two accounts on this box, let's say "admin" (an admin account) and "me" (a non-admin account).  "admin" is almost never logged in; "me" is almost always logged in.

I created the tasks from within Reflect, while logged in as "me", but with elevated privileges.  "admin" was not logged in during any of this.  Closed Reflect.  Still logged in as "me", opened Task Scheduler but via "Run as administrator".  In each backup task, "When running the task, use the following user account:" was set to "me".  I clicked "Change User or Group ..." and typed in "admin".  Closed that dialog, and then when closing the Properties window too the program asked for "admin"'s password.  Which, of course, I gave it.  "Run whether user is logged in or not" was the initial selected state, and I didn't change that.

That's all.  I didn't change anything else.
Richard V.
Richard V.
Most Valuable Professional
Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)
Group: Forum Members
Posts: 2K, Visits: 8K
Thanks for that.  I thought I had done just exactly what you so kindly described in detail, but couldn't get it to work.  It kept giving me those 0x800702E4 Elevation Required errors.  I'll keep testing and trying.  It would be an ideal workaround for the current problem, both leaving the MR listing intact and allowing the scheduled task to run unattended, unlike the other two workaround suggestions.  There's little doubt that the underlying Task Scheduler 1.0 API issue is somehow related to its credentials handling.


Regards, Richard V. ("Arvy")
https://forum.macrium.com/uploads/images/afc5d4fe-5d25-4e25-be94-185e.png

Edited 7 August 2016 8:07 PM by Arvy
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search