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
> > > > > >
> > > > >
> > > > >
> > > > >