WINDOWS XP SP2 - TASK SCHEDULER CRASHING AT RANDOM - PLEASE HELP

wrote:

I've had no trouble running scheduled tasks unattended under Windows
XP until SP2 was installed. When I checked the log, I frequently come
across the new error in the logs

Result: The task completed with an exit code of (c0000142).

This seems to occur at random but even more frequently day by day.
None of this happened when I was on Windows XP SP1a.

Please help.
http://support.microsoft.com/default.aspx?kbid=884130
Now they can add task scheduler to the list!

How do you work that out. The message indicates the program was started =
sucessfully. The exit code is application defined and may mean =
everything went ok.=20

--=20
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/...392635123.html

"AnnonUser" wrote in message =
...
wrote:
=20
I've had no trouble running scheduled tasks unattended under Windows
XP until SP2 was installed. When I checked the log, I frequently =
come
across the new error in the logs
=20
Result: The task completed with an exit code of (c0000142).
=20
This seems to occur at random but even more frequently day by day.
None of this happened when I was on Windows XP SP1a.
=20
Please help.
http://support.microsoft.com/default.aspx?kbid=3D884130
Now they can add task scheduler to the list!

David Candy wrote:

How do you work that out. The message indicates the program was started sucessfully. The exit code is application defined and may mean everything went ok.

Hey, all I'm saying is -- it worked before and doesn't work now and in
between was the SP2 install. THAT'S how I worked it out.
SP2 is a DISASTER

It working now. That's what the message said. If your program isn't =
working (rather than task scheduler), and one can't tell that from the =
message (though it would be unusual but not unknown), then you need to =
talk about the program not task scheduler.

Some Norton's product uses 42 to indicate OK. Most programs return 0 =
(because they don't specify exit codes). Some programs use the exit code =
to indicate what happened (especially command line programs).
--=20
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/...392635123.html

"AnnonUser" wrote in message =
...
David Candy wrote:
=20
How do you work that out. The message indicates the program was =
started sucessfully. The exit code is application defined and may mean =
everything went ok.=20
=20
Hey, all I'm saying is -- it worked before and doesn't work now and in =

between was the SP2 install. THAT'S how I worked it out.
SP2 is a DISASTER