task scheduler keeps forgetting my password

[Guest]

I use the task scheduler to perform a daily incremental backup. I've entered
my password, and the task runs properly the first time. After the one
successful backup, however, the scheduler forgets my password and fails the
next day. I have to re-enter my password every day in order to get the task
to run, which rather defeats the purpose of scheduling it in the first place.

I've tried completely deleting the task and recreating it from scratch
through the Backup wizard, but the same problem reoccurs. I have co-workers
using the same procedure on their PCs successfully. What's happening?

 

[Pegasus \(MVP\)]

I use the task scheduler to perform a daily incremental backup. I've entered
my password, and the task runs properly the first time. After the one
successful backup, however, the scheduler forgets my password and fails the
next day. I have to re-enter my password every day in order to get the task
to run, which rather defeats the purpose of scheduling it in the first place.

I've tried completely deleting the task and recreating it from scratch
through the Backup wizard, but the same problem reoccurs. I have co-workers
using the same procedure on their PCs successfully. What's happening?

Try creating a simple scheduled task, e.g. by invoking this batch file:

@echo off
echo %date% %time% Start of task > c:\test.log
echo User=%UserName%, Path=%path% >> c:\test.log

See if it runs on two consecutive days, by examining c:\test.log. If it
works, add a third line to this batch file: The command line you copy
& paste out of the scheduled backup job.

 

[Guest]

I can see how this might be used as a successful workaround, but I'd really
like to know why this is occuring in the first place. I'm in a corporate
environment and not everyone is computer savvy. If this problem occurs (or is
currently occuring) with others following our basic process, I need a way to
correct it, not work around it. Thanks for the suggestion, but do you know,
or have an idea towards, what might be the root cause of the problem?

 

[Pegasus \(MVP\)]

I have used the Task Scheduler successfully for many years and I have
never come across an issue like yours. My approach to such problems
is usually to collect evidence, lots of it. In most cases this reveals the
underlying cause of the problem. If it does not then the evidence can
be used to lodge a support call with Microsoft. If the problem is caused
by a Windows bug then the call charge is refunded.

In the meantime, if the work-around works, use it!

 

[Guest]

....and it didn't work. It ran successfully the first day, and failed the
second. Not a clue as to why...

 

[Pegasus \(MVP\)]

"It did not work" is rather vague. What were the contents of
c:\test.log?

 

[Guest]

The batch file ran successfully the first day, recording the date & time, my
user account name, and a large string of path information. The second day,
the scheduled task was unable to run (because it "forgot" my password) and
the log file wasn't touched since the batch file was never executed. The
Scheduled Tasks window shows that the task status was "Could not start".

I didn't realize there was a detailed log file generated by the Task
Scheduler itself. Here's what it says about the failed attempt:

"test.job" (test.bat) 11/15/2005 12:00:00 PM ** ERROR **
The attempt to log on to the account associated with the task failed,
therefore, the task did not run.
The specific error is:
0x80070569: Logon failure: the user has not been granted the requested
logon type at this computer.
Verify that the task's Run-as name and password are valid and try again.

Does this additional information provide any more insight?

 

[Pegasus \(MVP\)]

Now we're talking! Run gpedit.msc, then follow this path:
Local Computer Policy / Computer Configuration / Windows Settings /
Security Settings / Local Policy / User Rights / Logon as a batch job.

Give the account used by the your task the right to log on as
a batch job.

 

[Guest]

The good news is, that's exactly where the problem is located. The bad news
is, I can't fix the problem. After some digging, it turns out my company
recently modified their policy settings without notifying the user community,
causing this problem to mysteriously appear. So the resolution now lies with
my IT department and trying to get the batch job logon privilege restored.

Many thanks for your help, Pegasus.

 

[Pegasus \(MVP\)]

Thanks for the feedback.

The good news is, that's exactly where the problem is located. The bad news
is, I can't fix the problem. After some digging, it turns out my company
recently modified their policy settings without notifying the user community,
causing this problem to mysteriously appear. So the resolution now lies with
my IT department and trying to get the batch job logon privilege restored.

Many thanks for your help, Pegasus.