Scheduled Tasks

[Howard Hartman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello.

I have an unusual problem on three Windows 2000 servers.

Each of these servers runs the same set of scheduled tasks which work fine
for a few hours.
After a few hours, however, the scheduled tasks stop running and fail with
"Could Not Start".

The event log shows that the scheduled tasks are failing because "The user
has not been granted the
requested logon type at this machine".

I've tried removing the tasks completely and rebuilding them and that did
not solve the problem.

Just resetting the password to what it currently is for the user in the
scheduled task properties is
enough to get the task working again for a few hours.

This server is Windows 2000 SP4.

Does anyone have an idea of what to look at or how to fix this?

Thanks.

- -----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
Comment: Digital signature guarantees authenticity

iQA/AwUBQYD9hN/hBQ7O4WklEQI+RwCgg0N+BC/jtbCpSY+kyzkQgBzyLKoAn1Hg
/VLFWQ0AHRdw6PWwP0GgDvjw
=v3sR
- -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
Comment: Digital signature guarantees authenticity

iQA/AwUBQYD9nN/hBQ7O4WklEQIejgCglILtjoiYtxDcw29WmSBXfDv/qG8AoMoA
0Ni4Gm5ql+RT/+q1KA0WUzof
=vTFg
-----END PGP SIGNATURE-----

 

[Pegasus \(MVP\)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello.

I have an unusual problem on three Windows 2000 servers.

Each of these servers runs the same set of scheduled tasks which work fine
for a few hours.
After a few hours, however, the scheduled tasks stop running and fail with
"Could Not Start".

The event log shows that the scheduled tasks are failing because "The user
has not been granted the
requested logon type at this machine".

I've tried removing the tasks completely and rebuilding them and that did
not solve the problem.

Just resetting the password to what it currently is for the user in the
scheduled task properties is
enough to get the task working again for a few hours.

This server is Windows 2000 SP4.

Does anyone have an idea of what to look at or how to fix this?

Thanks.

- -----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
Comment: Digital signature guarantees authenticity

iQA/AwUBQYD9hN/hBQ7O4WklEQI+RwCgg0N+BC/jtbCpSY+kyzkQgBzyLKoAn1Hg
/VLFWQ0AHRdw6PWwP0GgDvjw
=v3sR
- -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
Comment: Digital signature guarantees authenticity

iQA/AwUBQYD9nN/hBQ7O4WklEQIejgCglILtjoiYtxDcw29WmSBXfDv/qG8AoMoA
0Ni4Gm5ql+RT/+q1KA0WUzof
=vTFg
-----END PGP SIGNATURE-----

Did you check if your policy allows the selected account
to log in as a batch job?

 

[Howard Hartman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks for your reply.

Yes, I did check that. If that was not set correctly, the task wouldn't run
at all.
This is a monitoring task that runs every 10 minutes around the clock. It
has
worked fine for up to 6 hours, then fails. Once it fails, it does not
succeed again
until I intervene and reset the password.

I've seen Microsoft Knowledge Base article 811155 which describes this event
log
error as it relates to starting service. It does not talk about scheduled
tasks failing,
however I have a feeling the cause may be the same.

Howard

Did you check if your policy allows the selected account
to log in as a batch job?

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
Comment: Digital signature guarantees authenticity

iQA/AwUBQYEQIt/hBQ7O4WklEQIxAQCgzBIE/ma3Zzr4QVGhRmyK7nJ9dSMAnRHI
He4f1pI088bjrj/555ln9E4T
=IuVO
-----END PGP SIGNATURE-----

 

[Pegasus \(MVP\)]

There was a similar post in a different newsgroup a few days ago.
The OP ultimately resolved his problem by using at.exe to
schedule his jobs, instead of the Task Scheduler. It may be
necessary to change the Service Account in order for such
tasks to be able to access network resources - use the
Advanced pull down menu in the Task Scheduler.

To schedule a task to run every 10 minutes under at.exe:

for /L %h in (0,1,23) do for /L %m in (0,5,55) do at %h:%m
/every:m,t,w,th,f,s,su c:\tools\sometask.exe

(unwrap line)

 

[Howard Hartman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Can you please explain the numbers in the AT statement you provided? I
understand the syntax.

Thanks.

There was a similar post in a different newsgroup a few days ago.
The OP ultimately resolved his problem by using at.exe to
schedule his jobs, instead of the Task Scheduler. It may be
necessary to change the Service Account in order for such
tasks to be able to access network resources - use the
Advanced pull down menu in the Task Scheduler.

To schedule a task to run every 10 minutes under at.exe:

for /L %h in (0,1,23) do for /L %m in (0,5,55) do at %h:%m
/every:m,t,w,th,f,s,su c:\tools\sometask.exe

(unwrap line)

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
Comment: Digital signature guarantees authenticity

iQA/AwUBQYJ4j9/hBQ7O4WklEQLpmgCcCf/8+nQvOIcehMdtbw3B7obWKPIAn3Lk
PwC78KCqY7ieJOqsJ2rgqFzh
=JuOI
-----END PGP SIGNATURE-----

 

[Pegasus \(MVP\)]

Type in this modified line. It won't schedule any tasks but
all will become perfectly obvious!

for /L %h in (0,1,23) do for /L %m in (0,5,55) do echo %h:%m
/every:m,t,w,th,f,s,su c:\tools\sometask.exe
(unwrap line)