Re: scheduled tasks won't run

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Pegasus \(MVP\) (I.can_at_fly.com)
Date: 11/16/04


Date: Wed, 17 Nov 2004 09:40:14 +1100

It's a policy issue. Run gpedit.msc, then follow this path:

Local Computer Policy / Computer Configuration / Windows Settings /
Security Settings / Account Policies / Local Policies /
User Rights Assignments / Log on as a batch job.

The account used for the scheduled job must be listed under this
policy. If it is not listed then it will not be able to run a scheduled job.

"Rolf Barbakken" <notnoisy@alexandria.cc> wrote in message
news:uMHMLf$yEHA.1564@TK2MSFTNGP09.phx.gbl...
> Typical error in the Scheduled Tasks log:
>
> "ewa_export.job" (ewa_export.cmd) 15.11.2004 12:00:00 ** 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.
>
> I have entered the correct domain\username and password dozens of times,
and
> pressed "Apply" before closing the dialog just to make sure. The user does
> have "Log on as a batchjob" rights.
>
> "Rolf Barbakken" <notnoisy@alexandria.cc> wrote in message
> news:uCUVbQ$yEHA.2752@TK2MSFTNGP11.phx.gbl...
> > Thanks, but all our partitions are NTFS and the problem did not start
> during
> > the transition to Daylight Savings.
> >
> > "Pegasus (MVP)" <I.can@fly.com> wrote in message
> > news:em9PmQ#yEHA.3588@TK2MSFTNGP14.phx.gbl...
> > > Have a look at the post "Scheduled Tasks", posted in this newsgroup
> > > four hours before your own post.
> > >
> > >
> > > "Rolf Barbakken" <notnoisy@alexandria.cc> wrote in message
> > > news:%23vnn1v9yEHA.1292@TK2MSFTNGP10.phx.gbl...
> > > > On one Windows 2000 Server (latest SP) I have several scheduled
tasks
> > > > (.cmd-files) that are to be run every day.
> > > >
> > > > But lately none of the tasks run without me logging on and running
> them
> > > > manually. Only error in the list of scheduled tasks list is "Could
not
> > > > start".
> > > >
> > > > What could be the reason for this? The user set up to run the tasks
> have
> > > > "Log on as a batchjob" rights. No info or error is found in the
> > eventlogs.
> > > >
> > > > --
> > > > ________________________
> > > > Rolf Barbakken @ Questus ans
> > > > Technical Supervisor
> > > > Web: http://www.questus.no
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Relevant Pages

  • Re: Domain Admin account and lockout Policy
    ... have different account policies for different domain user accounts, ... Topics, Group Policy Management, Concepts, Group Policy Object Editor ... Default Domain Policy Group Policy object (GPO) or in a new GPO that ...
    (microsoft.public.windows.group_policy)
  • Re: Domain Admin account and lockout Policy
    ... have different account policies for different domain user accounts, ... Topics, Group Policy Management, Concepts, Group Policy Object Editor ... Default Domain Policy Group Policy object (GPO) or in a new GPO that ...
    (microsoft.public.windows.group_policy)
  • Re: Problems testiing GPO for password complexity on OU before changing default domain policy
    ... Account policies are only read at the domain level and you can only have one ... apply to the local machine account policy. ... The complex password policy is applied when I logon to the local machine but not when I logon with a domain user which is a member of the OU and security group within that OU. ...
    (microsoft.public.win2000.active_directory)
  • Re: Password Policy for remote users
    ... Account policies. ... You cannot alter the blanket policy for such ... the account policies are not in the User branch but ... a subset of account required to use smart card for login. ...
    (microsoft.public.security)
  • Re: Security Policy for OU?
    ... domain account the DC authenticates you - not the local SAM. ... applying the policy at a level whereby the domain controllers are not within ... > The account policies for domain users only apply if they are in the ...
    (microsoft.public.windows.server.active_directory)