G
Guest
I am trying to setup an overnight backup on my XP machine. I can run the
backup manually (by right-clicking on the task in the Task Scheduler and
choosing "Run") just fine at any time during the day. I leave for the day
and come back the next morning and the task shows "Could not start" in the
"Status" field. I've checked the log and it tells me that there is a logon
failure. If I try to manually run the task, it still won't start. If I go
into the properties for the task and set the password again (and only if I do
this. Logging off and logging back in, restarting, etc doesn't work) , the
task runs fine and will continue to work at any point that day that I want to
try it. Leave overnight, come back, problem returns. After doing some
Googling, I thought the problem was because the user I was running it as
didn't have the "Log on as a batch job" enabled in the Local Security Policy.
That didn't fix it, though. The problem also doesn't seem to appear with
any combination of locking the computer, logging off, etc. Only letting the
computer sit overnight seems to bring the problem. So all of the symptoms
seem to point to something being ran overnight that breaks the scheduler or
simply the date changing, but I can't seem to find any info out there about
either of these. Does anyone have any ideas?
backup manually (by right-clicking on the task in the Task Scheduler and
choosing "Run") just fine at any time during the day. I leave for the day
and come back the next morning and the task shows "Could not start" in the
"Status" field. I've checked the log and it tells me that there is a logon
failure. If I try to manually run the task, it still won't start. If I go
into the properties for the task and set the password again (and only if I do
this. Logging off and logging back in, restarting, etc doesn't work) , the
task runs fine and will continue to work at any point that day that I want to
try it. Leave overnight, come back, problem returns. After doing some
Googling, I thought the problem was because the user I was running it as
didn't have the "Log on as a batch job" enabled in the Local Security Policy.
That didn't fix it, though. The problem also doesn't seem to appear with
any combination of locking the computer, logging off, etc. Only letting the
computer sit overnight seems to bring the problem. So all of the symptoms
seem to point to something being ran overnight that breaks the scheduler or
simply the date changing, but I can't seem to find any info out there about
either of these. Does anyone have any ideas?