Schdule task issue

[Guest Adnan Wali]

I am having issue with schedule task, my task runs fine for 1 days and then

stops giving error

0x80070569(he 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.)

 

I use the same the password and it started again for one day and again same

issue. I am not sure what the issue is. is it a bug or what

[Guest Meinolf Weber]

Re: Schdule task issue

 

Hello Adnan,

 

Check under your group policies that the account is added to the "user rights

assignment" LOGON AS A BATCH JOB

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I am having issue with schedule task, my task runs fine for 1 days and

> then

> stops giving error

> 0x80070569(he 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.)

> I use the same the password and it started again for one day and again

> same issue. I am not sure what the issue is. is it a bug or what

>

[Guest Adnan Wali]

Re: Schdule task issue

 

Hello Meinolf- Thanks fro the response Just checked that account is already

have logon as batch job right

 

"Meinolf Weber" wrote:

> Hello Adnan,

>

> Check under your group policies that the account is added to the "user rights

> assignment" LOGON AS A BATCH JOB

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

> > I am having issue with schedule task, my task runs fine for 1 days and

> > then

> > stops giving error

> > 0x80070569(he 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.)

> > I use the same the password and it started again for one day and again

> > same issue. I am not sure what the issue is. is it a bug or what

> >

>

>

>

[Guest Pegasus \(MVP\)]

Re: Schdule task issue

 

I would create a new account for the scheduled tasks and

see if the problem persists.

 

"Adnan Wali" <AdnanWali@discussions.microsoft.com> wrote in message

news:25BE708C-C202-4E07-9FD2-185FB09EB226@microsoft.com...

> Hello Meinolf- Thanks fro the response Just checked that account is

> already

> have logon as batch job right

>

> "Meinolf Weber" wrote:

>

>> Hello Adnan,

>>

>> Check under your group policies that the account is added to the "user

>> rights

>> assignment" LOGON AS A BATCH JOB

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>

>> > I am having issue with schedule task, my task runs fine for 1 days and

>> > then

>> > stops giving error

>> > 0x80070569(he 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.)

>> > I use the same the password and it started again for one day and again

>> > same issue. I am not sure what the issue is. is it a bug or what

>> >

>>

>>

>>

[Guest ztruelove]

Re: Schdule task issue

 

Adnan, were you able to get this resolved. I'm having the same issue with a

task.

 

"Adnan Wali" wrote:

> Hello Meinolf- Thanks fro the response Just checked that account is already

> have logon as batch job right

>

> "Meinolf Weber" wrote:

>

> > Hello Adnan,

> >

> > Check under your group policies that the account is added to the "user rights

> > assignment" LOGON AS A BATCH JOB

> >

> > Best regards

> >

> > Meinolf Weber

> > Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> > no rights.

> > ** Please do NOT email, only reply to Newsgroups

> > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >

> > > I am having issue with schedule task, my task runs fine for 1 days and

> > > then

> > > stops giving error

> > > 0x80070569(he 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.)

> > > I use the same the password and it started again for one day and again

> > > same issue. I am not sure what the issue is. is it a bug or what

> > >

> >

> >

> >

[Guest Adnan Wali]

Re: Schdule task issue

 

not really. having same issue

 

"ztruelove" wrote:

> Adnan, were you able to get this resolved. I'm having the same issue with a

> task.

>

> "Adnan Wali" wrote:

>

> > Hello Meinolf- Thanks fro the response Just checked that account is already

> > have logon as batch job right

> >

> > "Meinolf Weber" wrote:

> >

> > > Hello Adnan,

> > >

> > > Check under your group policies that the account is added to the "user rights

> > > assignment" LOGON AS A BATCH JOB

> > >

> > > Best regards

> > >

> > > Meinolf Weber

> > > Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> > > no rights.

> > > ** Please do NOT email, only reply to Newsgroups

> > > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> > >

> > > > I am having issue with schedule task, my task runs fine for 1 days and

> > > > then

> > > > stops giving error

> > > > 0x80070569(he 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.)

> > > > I use the same the password and it started again for one day and again

> > > > same issue. I am not sure what the issue is. is it a bug or what

> > > >

> > >

> > >

> > >

[Guest Mikhail]

Re: Schedule task issue

 

Re: Schedule task issue

 

What helped me with this case was:

 

1. Allow task user to log on as batch job (Computer Configuration/Windows

Settings/Security Settings/Local Policies/User Rights Assignment/Log on as

batch job).

2. STOP SCHEDULER.

3. Delete old task.

4. Create new task.

5. START SCHEDULER.

 

Note that it does not work without stopping task scheduler, and maybe giving

user group the right to logon as batch job will do as well.

 

W2K3 SRV SP1

 

 

 

"Adnan Wali" wrote:

> not really. having same issue

>

> "ztruelove" wrote:

>

> > Adnan, were you able to get this resolved. I'm having the same issue with a

> > task.

> >

> > "Adnan Wali" wrote:

> >

> > > Hello Meinolf- Thanks fro the response Just checked that account is already

> > > have logon as batch job right

> > >

> > > "Meinolf Weber" wrote:

> > >

> > > > Hello Adnan,

> > > >

> > > > Check under your group policies that the account is added to the "user rights

> > > > assignment" LOGON AS A BATCH JOB

> > > >

> > > > Best regards

> > > >

> > > > Meinolf Weber

> > > > Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> > > > no rights.

> > > > ** Please do NOT email, only reply to Newsgroups

> > > > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> > > >

> > > > > I am having issue with schedule task, my task runs fine for 1 days and

> > > > > then

> > > > > stops giving error

> > > > > 0x80070569(he 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.)

> > > > > I use the same the password and it started again for one day and again

> > > > > same issue. I am not sure what the issue is. is it a bug or what

> > > > >

> > > >

> > > >

> > > >

[Guest Steven Davidson]

Re: Schedule task issue

 

Re: Schedule task issue

 

It seems that this is a very common problem. I've run into this issue twice

in the last month. In both cases it was on a Windows XP Pro w/sp2. I've

seen people have this problem using Vista and Windows Server 2003 R2 as well.

I've never been able to find a solution to this and I haven't found any

solid leads as to the cause. In one instance, I had the task scheduled to

run at system startup. In another case, the task was scheduled to run every

10 minutes. In both cases I created an account specifically for running the

task and I made the account a local administrator just to take rights out of

the equation. I've googled the crap out of this and have had no luck. So

here's what I do as a workaround. I create a batch job with a loop control.

I made a small program in VB that evokes the sleep api call in the loop. It's

not a perfect solution but it's good if you have a task that runs every x

minutes. If you use a batch job with a loop control, at least the task only

has one chance of not starting. Then it's good until you restart the system.

So, for instance, in the case where I have a job that I run every 10

minutes, I have a loop in the batch job that sleeps for 600 seconds. I

launch the batch job with a scheduled task and it runs indefinately (until I

manually stop it or I restart the system). Then I set this scheduled task to

start at system startup. Then I just have to remember to check the scheduled

task when I reboot the computer and then I can forget about it.

 

At this point, I'd gladly chip in to open a tech support call with Microsoft

because this is clearly a bug...er, I mean "security feature" that they need

to rethink.

 

"Mikhail" wrote:

> What helped me with this case was:

>

> 1. Allow task user to log on as batch job (Computer Configuration/Windows

> Settings/Security Settings/Local Policies/User Rights Assignment/Log on as

> batch job).

> 2. STOP SCHEDULER.

> 3. Delete old task.

> 4. Create new task.

> 5. START SCHEDULER.

>

> Note that it does not work without stopping task scheduler, and maybe giving

> user group the right to logon as batch job will do as well.

>

> W2K3 SRV SP1

>

>

>

> "Adnan Wali" wrote:

>

> > not really. having same issue

> >

> > "ztruelove" wrote:

> >

> > > Adnan, were you able to get this resolved. I'm having the same issue with a

> > > task.

> > >

> > > "Adnan Wali" wrote:

> > >

> > > > Hello Meinolf- Thanks fro the response Just checked that account is already

> > > > have logon as batch job right

> > > >

> > > > "Meinolf Weber" wrote:

> > > >

> > > > > Hello Adnan,

> > > > >

> > > > > Check under your group policies that the account is added to the "user rights

> > > > > assignment" LOGON AS A BATCH JOB

> > > > >

> > > > > Best regards

> > > > >

> > > > > Meinolf Weber

> > > > > Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> > > > > no rights.

> > > > > ** Please do NOT email, only reply to Newsgroups

> > > > > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> > > > >

> > > > > > I am having issue with schedule task, my task runs fine for 1 days and

> > > > > > then

> > > > > > stops giving error

> > > > > > 0x80070569(he 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.)

> > > > > > I use the same the password and it started again for one day and again

> > > > > > same issue. I am not sure what the issue is. is it a bug or what

> > > > > >

> > > > >

> > > > >

> > > > >

[Guest Andrew Duey]

Any headway on dying tasks?

 

Any headway on dying tasks?

 

We are seeing the same problem as described on our Windows 2003 server (64-bit). We have jobs that run every ten minutes for 14 hours. We have 5 different tasks and all at once they all cease to start. We reset the password on one of them and then they all start as scheduled.

 

I think we've figured out that after resetting the password the tasks will start properly for the next 10 hours and then cease starting as scheduled. We're not sure were 10 hour is coming from (I've checked our group policy and we don't have anything set for a 10 hour time limit).

[Guest Pegasus \(MVP\)]

Re: Any headway on dying tasks?

 

Re: Any headway on dying tasks?

 

 

<Andrew Duey> wrote in message news:2008616123737andrew@duey.biz...

> We are seeing the same problem as described on our Windows 2003 server

> (64-bit). We have jobs that run every ten minutes for 14 hours. We have

> 5 different tasks and all at once they all cease to start. We reset the

> password on one of them and then they all start as scheduled.

>

> I think we've figured out that after resetting the password the tasks will

> start properly for the next 10 hours and then cease starting as scheduled.

> We're not sure were 10 hour is coming from (I've checked our group policy

> and we don't have anything set for a 10 hour time limit).

=============

- What does the Event Viewer report?

- What does the Task Scheduler log file say?

[Guest Andrew Duey]

Solved!!! (at least for me)

 

Solved!!! (at least for me)

 

I got it fixed! (at least for my servers)

 

I found that there as a group policy applied to domain controllers (which must have been there by default as this is a 3 month old domain and I didn't put that policy there). In the "Default Domain Contollers Policy" I found that the "Log on as batch service" setting was being defined:

 

"Default Domain Contollers Policy"\Computer configuration\windows settings\security settings\local policies\user rights assignment\Log on as batch service

 

What would apparently happen was when the job was setup (or the password reset) it would grant the user accoutn Log on as batch service permissions. Then the next time the group policy update came down it would overwrite those setting and NOT have the proper account listed.

 

To fix the problem I added Domain\DomainAdmin to the policy setting in the group policy and then ran "gpedit /force" on the problem server to force that policy update. Moments later my job was starting like normal.

 

The key was that resetting the password would cause the task schedule to update the local security policy and let the task run. Then when the group policy update came down it would wipe out the setting in the local security policy. Some time later I would reset the password, and the task scheduler would add that account back to the Log on as batch service security policy until the group policy pushed another updated, and round and round we'd go.

 

I wanted to post it up for anyone who still is scratching their head about this one!

 

--Andrew Duey, MCSE NT4

[Guest Pegasus \(MVP\)]

Re: Solved!!! (at least for me)

 

Re: Solved!!! (at least for me)

 

 

<Andrew Duey> wrote in message news:200861613449andrew@duey.biz...

>I got it fixed! (at least for my servers)

>

> I found that there as a group policy applied to domain controllers (which

> must have been there by default as this is a 3 month old domain and I

> didn't put that policy there). In the "Default Domain Contollers Policy"

> I found that the "Log on as batch service" setting was being defined:

>

> "Default Domain Contollers Policy"\Computer configuration\windows

> settings\security settings\local policies\user rights assignment\Log on as

> batch service

>

> What would apparently happen was when the job was setup (or the password

> reset) it would grant the user accoutn Log on as batch service

> permissions. Then the next time the group policy update came down it

> would overwrite those setting and NOT have the proper account listed.

>

> To fix the problem I added Domain\DomainAdmin to the policy setting in the

> group policy and then ran "gpedit /force" on the problem server to force

> that policy update. Moments later my job was starting like normal.

>

> The key was that resetting the password would cause the task schedule to

> update the local security policy and let the task run. Then when the

> group policy update came down it would wipe out the setting in the local

> security policy. Some time later I would reset the password, and the task

> scheduler would add that account back to the Log on as batch service

> security policy until the group policy pushed another updated, and round

> and round we'd go.

>

> I wanted to post it up for anyone who still is scratching their head about

> this one!

>

> --Andrew Duey, MCSE NT4

 

Thanks for the report. When discussing your next problem,

consider cross-posting instead of multi-posting it:

http://www.blakjak.demon.co.uk/mul_crss.htm