Scheduled task: it always finishes with error 0x80

[David Lightman Robles]

Hi all,

I´m running Windows XP Prof (standalone, not in a domain and all SPs and
patches applied) and I´m trying to set a scheduled task to do some
maintenance during the night. The problem is that it does not work if I´m
not logged in. If nobody is logged in the machine, the task (a batch file)
tries to start and finishes with error 0x80. However, when I´m logged in, go
to Scheduled Tasks folder right click it and select execute, it starts and
works perfectly.

It is nothing to do with the contents of the batch file, because trying to
simplify the problem, I modified the batch so it is now:

echo it works > c:\executed.txt

Simple, isn´t it? It is nothing to do with passwords either: I doble and
triple checked it and the password for the scheduled task is ok.

Any ideas? Is this behaviour by design? Can´t I schedule a task to be run
when nobody is logged in? I hope this is not the case.

Thanks in advance.

[Kelly]

Hi David,

Suggestion:

Scheduled Tasks - Auto Start (getting tasks to run when no one is
logged on). If you follow these steps, the shedlgu.txt file will be
replaced without any information other than system start-up information upon
the first boot.

Go to Start/Run/Msconfig. Click Selective Startup and uncheck Load System
Services, click ok. Reboot.

Upon reboot, click OK to the first Window that indicates that you have
selected "Selective Startup". When the System Configuration Utility
reappears, Check the Normal Startup Box.

Then go to Start/Search and type in: schedlgu.txt. When it appears, right
click on the file and delete it. Reboot.

You will now have a new Task Scheduler Log File. It can be checked by going
to Start/Search and typing in: schedlgu.txt. Appearing will be your new Task
Scheduler Log.

--
All the Best,
Kelly

MS-MVP Win98/XP [AE-Windows® XP]
Troubleshooting Windows XP
http://www.kellys-korner-xp.com
http://www.kellys-korner-xp.com/xp_abc.htm
http://www.kellys-korner-xp.com/xp_tweaks.htm

Top 10 Frequently Asked Questions and Answers
http://www.kellys-korner-xp.com/top10faqs.htm


"David Lightman Robles" > wrote in message
...
> Hi all,
>
> I´m running Windows XP Prof (standalone, not in a domain and all SPs and
> patches applied) and I´m trying to set a scheduled task to do some
> maintenance during the night. The problem is that it does not work if I´m
> not logged in. If nobody is logged in the machine, the task (a batch file)
> tries to start and finishes with error 0x80. However, when I´m logged in,
go
> to Scheduled Tasks folder right click it and select execute, it starts and
> works perfectly.
>
> It is nothing to do with the contents of the batch file, because trying to
> simplify the problem, I modified the batch so it is now:
>
> echo it works > c:\executed.txt
>
> Simple, isn´t it? It is nothing to do with passwords either: I doble and
> triple checked it and the password for the scheduled task is ok.
>
> Any ideas? Is this behaviour by design? Can´t I schedule a task to be run
> when nobody is logged in? I hope this is not the case.
>
> Thanks in advance.
>
>

[David Lightman Robles]

Hi Kelly, and thanks for your quick hint.

I have just tried what you suggested but the only thing that your procedure
gets is for me to be able to delete the old log file for the scheduled
tasks. I suppose that having a new empty logfile might help to understand
the problem, but it does not help to solve it in any way. It still happens:
the task finishes with error 0x80 when nobody is logged in.

Here are the contents of the new logfile having tried to execute the task
twice:


"Servicio programador de tareas"
Iniciado a las 13/04/2003 12:09:19
"UNISON.job" (DoAll.bat)
Iniciado el 13/04/2003 12:11:00
"UNISON.job" (DoAll.bat)
Finalizó el 13/04/2003 12:11:00
Resultado: La tarea se completó con un código de salida de (80).
"UNISON.job" (DoAll.bat)
Iniciado el 13/04/2003 12:12:02
"UNISON.job" (DoAll.bat)
Finalizó el 13/04/2003 12:12:03
Resultado: La tarea se completó con un código de salida de (80).
[ ***** Entrada más reciente sobre esta línea ***** ]



My OS is Spanish but i hope it has nothing to do with my problem :). The
logfile, somewhat translated it says:

"Scheduled Tasks Service"
Started at 13/04/2003 12:09:19
"UNISON.job" (DoAll.bat)
Started on 13/04/2003 12:11:00
"UNISON.job" (DoAll.bat)
Finished on 13/04/2003 12:11:00
Result: The task completed with an output code of (80).
[2nd run, the same with other date/time value]
[ ***** Most recent entry over this line ***** ]

As I can see, this log file does not give any more information as I had
before. The evenlog does not show any error nor information about this
either.

Any other idea? Thanks again.


"Kelly" > escribió en el mensaje
...
> Hi David,
>
> Suggestion:
>
> Scheduled Tasks - Auto Start (getting tasks to run when no one is
> logged on). If you follow these steps, the shedlgu.txt file will be
> replaced without any information other than system start-up information
upon
> the first boot.
>
> Go to Start/Run/Msconfig. Click Selective Startup and uncheck Load System
> Services, click ok. Reboot.
>
> Upon reboot, click OK to the first Window that indicates that you have
> selected "Selective Startup". When the System Configuration Utility
> reappears, Check the Normal Startup Box.
>
> Then go to Start/Search and type in: schedlgu.txt. When it appears, right
> click on the file and delete it. Reboot.
>
> You will now have a new Task Scheduler Log File. It can be checked by
going
> to Start/Search and typing in: schedlgu.txt. Appearing will be your new
Task
> Scheduler Log.
>
> --
> All the Best,
> Kelly
>
> MS-MVP Win98/XP [AE-Windows® XP]
> Troubleshooting Windows XP
> http://www.kellys-korner-xp.com
> http://www.kellys-korner-xp.com/xp_abc.htm
> http://www.kellys-korner-xp.com/xp_tweaks.htm
>
> Top 10 Frequently Asked Questions and Answers
> http://www.kellys-korner-xp.com/top10faqs.htm
>
>
> "David Lightman Robles" > wrote in
message
> ...
> > Hi all,
> >
> > I´m running Windows XP Prof (standalone, not in a domain and all SPs and
> > patches applied) and I´m trying to set a scheduled task to do some
> > maintenance during the night. The problem is that it does not work if
I´m
> > not logged in. If nobody is logged in the machine, the task (a batch
file)
> > tries to start and finishes with error 0x80. However, when I´m logged
in,
> go
> > to Scheduled Tasks folder right click it and select execute, it starts
and
> > works perfectly.
> >
> > It is nothing to do with the contents of the batch file, because trying
to
> > simplify the problem, I modified the batch so it is now:
> >
> > echo it works > c:\executed.txt
> >
> > Simple, isn´t it? It is nothing to do with passwords either: I doble and
> > triple checked it and the password for the scheduled task is ok.
> >
> > Any ideas? Is this behaviour by design? Can´t I schedule a task to be
run
> > when nobody is logged in? I hope this is not the case.
> >
> > Thanks in advance.
> >
> >
>

[mikey]

try this

Task Scheduler Fix

A scheduled task can be run

without passwords

For PRO

Under Administrative Tools

Local Security settings >Local Policies>Security options.

In the right hand pane (third down)

Accounts: Limit local account use of blank passwords to console logon only.

This is enabled by default --disable it.









"David Lightman Robles" > wrote in message ...
Hi all,

I´m running Windows XP Prof (standalone, not in a domain and all SPs and
patches applied) and I´m trying to set a scheduled task to do some
maintenance during the night. The problem is that it does not work if I´m
not logged in. If nobody is logged in the machine, the task (a batch file)
tries to start and finishes with error 0x80. However, when I´m logged in, go
to Scheduled Tasks folder right click it and select execute, it starts and
works perfectly.

It is nothing to do with the contents of the batch file, because trying to
simplify the problem, I modified the batch so it is now:

echo it works > c:\executed.txt

Simple, isn´t it? It is nothing to do with passwords either: I doble and
triple checked it and the password for the scheduled task is ok.

Any ideas? Is this behaviour by design? Can´t I schedule a task to be run
when nobody is logged in? I hope this is not the case.

Thanks in advance.



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.471 / Virus Database: 269 - Release Date: 4/10/2003

[David Lightman Robles]

I´m sorry, but that doesn´t work either. Still the same behaviour. More ideas?
"mikey" > escribió en el mensaje ...
try this

Task Scheduler Fix

A scheduled task can be run

without passwords

For PRO

Under Administrative Tools

Local Security settings >Local Policies>Security options.

In the right hand pane (third down)

Accounts: Limit local account use of blank passwords to console logon only.

This is enabled by default --disable it.









"David Lightman Robles" > wrote in message ...
Hi all,

I´m running Windows XP Prof (standalone, not in a domain and all SPs and
patches applied) and I´m trying to set a scheduled task to do some
maintenance during the night. The problem is that it does not work if I´m
not logged in. If nobody is logged in the machine, the task (a batch file)
tries to start and finishes with error 0x80. However, when I´m logged in, go
to Scheduled Tasks folder right click it and select execute, it starts and
works perfectly.

It is nothing to do with the contents of the batch file, because trying to
simplify the problem, I modified the batch so it is now:

echo it works > c:\executed.txt

Simple, isn´t it? It is nothing to do with passwords either: I doble and
triple checked it and the password for the scheduled task is ok.

Any ideas? Is this behaviour by design? Can´t I schedule a task to be run
when nobody is logged in? I hope this is not the case.

Thanks in advance.



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.471 / Virus Database: 269 - Release Date: 4/10/2003

[mikey]

is it totally out of the question to just leave someone logged in,. preferably the person whose account the scheduled task was created for.







"David Lightman Robles" > wrote in message ...
I´m sorry, but that doesn´t work either. Still the same behaviour. More ideas?
"mikey" > escribió en el mensaje ...
try this

Task Scheduler Fix

A scheduled task can be run

without passwords

For PRO

Under Administrative Tools

Local Security settings >Local Policies>Security options.

In the right hand pane (third down)

Accounts: Limit local account use of blank passwords to console logon only.

This is enabled by default --disable it.









"David Lightman Robles" > wrote in message ...
Hi all,

I´m running Windows XP Prof (standalone, not in a domain and all SPs and
patches applied) and I´m trying to set a scheduled task to do some
maintenance during the night. The problem is that it does not work if I´m
not logged in. If nobody is logged in the machine, the task (a batch file)
tries to start and finishes with error 0x80. However, when I´m logged in, go
to Scheduled Tasks folder right click it and select execute, it starts and
works perfectly.

It is nothing to do with the contents of the batch file, because trying to
simplify the problem, I modified the batch so it is now:

echo it works > c:\executed.txt

Simple, isn´t it? It is nothing to do with passwords either: I doble and
triple checked it and the password for the scheduled task is ok.

Any ideas? Is this behaviour by design? Can´t I schedule a task to be run
when nobody is logged in? I hope this is not the case.

Thanks in advance.



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.471 / Virus Database: 269 - Release Date: 4/10/2003