Scheduled task could not run

[Rick S]

I have several scheduled tasks that have been running for
months. They have suddenly stopped running. The status
is "Could Not Start" and here's the log on one
8/16/2004 12:01:00 AM ** 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.<<<<<<<<<<<<<

If I reenter the password on the task after rebooting they
usually work for awhile but they will eventually quit. If
I don't reenter the passwords after rebooting they usually
don't run but occassionally will. It is very strange.

I don't know what has changed. I don't recall any changes
to the user setup or any software changes (no hotfixes or
changes to norton etc) that coincide with the start of the
problem but I am not positive of that.

I am running XP Pro sp1. Thanks for any help.

Rick

 

[Jeff Rebeiro]

The password for the account you specified may have been changed and you did
not update the scheduled task. Double-Click on the task and under the Task
tab hit Set Password. Enter the current password for the account specified
and hit OK. If the password is wrong or incorrect you will get an error as
soon as you hit OK.

 

[Rick S]

I've been reentering the passwords daily for a week now.
The processes almost always fail after a reboot unless I
do so (I have seen one run without reentering the password
but then it failed the next reboot so I don't see a
pattern).

Yesterday I reentered all the passwords before I left
work. Onvernight one of the processes worked but three
others failed. They all use the same user/password.

 

[Otacon]

I'm also getting the exact same thing and I cant explain it. Did this ever get resolved?

 

[timeliner]

Task could not run

Hy - me too!



Does anybody find the reasons for that problem?



Regardes, Thomas

 

[blum0111]

I'm having the same problems, as well. I'll create a scheduled task, it will run fine the first time, then, after that, it continues to fail until I manually reset the password again. Very frustrating...
The task I'm running is on a remote server, so I've tried opening up the "Log on as a batch job" policy to administrators and that doesn't seem to help.
Any help would be greatly appreciated!
dave

 

[pap502]

Try setting local security policy

I had similar problems, also after setting the password.
You may want to try granting the user who is running the scheduled task the "Create Global Objects" local security policy.

Start -> Settings -> Control Panel -> Adminitrative Tools
Click on "Local Security Policy"
Double-click on "Create global obejcts"
Add the user or group who is running the scheduled task to that local security setting.
Click OK.
(this may vary, depending on what flavor of Windows you are using.)

I have found that this helps with running some appas via Citrix as well.
Hope this helps.

 

[pattywmom]

Look at this

We too are having the same problem, and it seems to be related to a GPO. If you submit your task to run and while waiting for it to start you perform a GPUPDATE on the server in question, the task will not run.

We're investigating a potential GPO issue, but not convinced - anyone?

 

[rypaul]

Here is what solved this for me

I checked my Domain server for the Domain security policy and sure enough
under Log on as batch job the administrator account I was trying to use was missing from the list of users. So what was happening was that after I would set the password for the sheduled task on the workstation in the morning which puts the account under the computer's local security policy "Log on as batch job", the Domain policy would get enforced sometime during the next 24 hrs effectively undoing my change. So basically if you are on a Domain the log on as batch job policy needs to be changed on the server not the actual computer that you are trying to run the task.
Hope this helps at least one person out there

 

[ravikumar1985]

This is the Problem am also facing. Need more help

Hi Paul and All,

Am also facing the same problem as am in a domain and the root cause mentioned by Paul holds correct. He says... 'basically if you are on a Domain the log on as batch job policy needs to be changed on the server not the actual computer that you are trying to run the task.'

In the solution.. it was mentioned.. 'log on as batch job policy needs to be changed on the server'. Can I have more clarification on this.. per my understanding.. the solution is.. 'get your name listed on the domain's log on as batch job policy?'

Am i correct in my understanding.. If not what should I ask my domain admin to give me?

Please help and your suggestions will help me great.

Thanking you in advance..
Ravi