Task Scheduler 0x80 errors

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

Guest
Hi,

We have problems with scheduled tasks failing on windows 2000. A reboot
solves this but we cannot get to the bottom of the problem. It's Sp4 and
there's no Human Interface Devices service. I've tried making jobs with the
AT command, assigning runas service and bath permissions and pretty much
worked through a lot of search results. It seems to be about every 7 days it
fails. Can anyone shed light on this? There is nothing in event logs (app
and system).

Task log attached, job names aren't actually xxxxxxxxxx lol.

"xxxxxxxxxx.job" (runxxxxx.bat)
Started 06/10/2008 23:45:00
"xxxxxxxxx.job" (runxxxxx.bat)
Finished 06/10/2008 23:49:14
Result: The task completed with an exit code of (0).
"Caxxxxx.job" (Caxxxxx.sql)
Started 06/10/2008 23:50:00
Started indirectly, through a shortcut; task finish will not be logged.
"ZMFxxxxx.job" (zmfxxxxx.sql)
Started 06/10/2008 23:55:00
Started indirectly, through a shortcut; task finish will not be logged.
"runxxxxxC01.job" (runxxxxxxxxxxC01.bat)
Started 06/10/2008 23:59:00
"runZxxxxxxxx.job" (runxxxxxxxxxxxxx.bat)
Finished 06/10/2008 23:59:00
Result: The task completed with an exit code of (80).
"copxxxxxxx.job" (copyxxxxxxxx.bat)
Started 07/10/2008 19:55:00
"copyxxxxxx.job" (copyxxxxxxxx.bat)
Finished 07/10/2008 19:55:00
Result: The task completed with an exit code of (80).
"Artixxxxxxxxxxxxx.job" (backstart.bat)
Started 07/10/2008 20:05:00
"Artixxxxxxxxxxxxx.job" (backstart.bat)
Finished 07/10/2008 20:05:00
Result: The task completed with an exit code of (80).
"runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
Started 07/10/2008 20:10:00
"runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
Finished 07/10/2008 20:10:00
Result: The task completed with an exit code of (80).

Thanks

Paul
 
Re: Task Scheduler 0x80 errors


"Paul" <chewbacca@wookie.org> wrote in message
news:Ouynw%23gKJHA.4908@TK2MSFTNGP02.phx.gbl...
> Hi,
>
> We have problems with scheduled tasks failing on windows 2000. A reboot
> solves this but we cannot get to the bottom of the problem. It's Sp4 and
> there's no Human Interface Devices service. I've tried making jobs with
> the
> AT command, assigning runas service and bath permissions and pretty much
> worked through a lot of search results. It seems to be about every 7 days
> it
> fails. Can anyone shed light on this? There is nothing in event logs (app
> and system).
>
> Task log attached, job names aren't actually xxxxxxxxxx lol.
>
> "xxxxxxxxxx.job" (runxxxxx.bat)
> Started 06/10/2008 23:45:00
> "xxxxxxxxx.job" (runxxxxx.bat)
> Finished 06/10/2008 23:49:14
> Result: The task completed with an exit code of (0).
> "Caxxxxx.job" (Caxxxxx.sql)
> Started 06/10/2008 23:50:00
> Started indirectly, through a shortcut; task finish will not be logged.
> "ZMFxxxxx.job" (zmfxxxxx.sql)
> Started 06/10/2008 23:55:00
> Started indirectly, through a shortcut; task finish will not be logged.
> "runxxxxxC01.job" (runxxxxxxxxxxC01.bat)
> Started 06/10/2008 23:59:00
> "runZxxxxxxxx.job" (runxxxxxxxxxxxxx.bat)
> Finished 06/10/2008 23:59:00
> Result: The task completed with an exit code of (80).
> "copxxxxxxx.job" (copyxxxxxxxx.bat)
> Started 07/10/2008 19:55:00
> "copyxxxxxx.job" (copyxxxxxxxx.bat)
> Finished 07/10/2008 19:55:00
> Result: The task completed with an exit code of (80).
> "Artixxxxxxxxxxxxx.job" (backstart.bat)
> Started 07/10/2008 20:05:00
> "Artixxxxxxxxxxxxx.job" (backstart.bat)
> Finished 07/10/2008 20:05:00
> Result: The task completed with an exit code of (80).
> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
> Started 07/10/2008 20:10:00
> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
> Finished 07/10/2008 20:10:00
> Result: The task completed with an exit code of (80).
>
> Thanks
>
> Paul


Task Scheduler return codes are generated by the command you schedule, or by
the last command in a batch file if it's a batch file you're scheduling.
What exactly are you scheduling?
 
Re: Task Scheduler 0x80 errors

It's various copy commands, batch files to copy out files and copy in a new
blank file. After a reboot they work fine for abotu 7 days then fail with
0x80


"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:e$rddviKJHA.5704@TK2MSFTNGP02.phx.gbl...
>
> "Paul" <chewbacca@wookie.org> wrote in message
> news:Ouynw%23gKJHA.4908@TK2MSFTNGP02.phx.gbl...
>> Hi,
>>
>> We have problems with scheduled tasks failing on windows 2000. A reboot
>> solves this but we cannot get to the bottom of the problem. It's Sp4 and
>> there's no Human Interface Devices service. I've tried making jobs with
>> the
>> AT command, assigning runas service and bath permissions and pretty much
>> worked through a lot of search results. It seems to be about every 7 days
>> it
>> fails. Can anyone shed light on this? There is nothing in event logs (app
>> and system).
>>
>> Task log attached, job names aren't actually xxxxxxxxxx lol.
>>
>> "xxxxxxxxxx.job" (runxxxxx.bat)
>> Started 06/10/2008 23:45:00
>> "xxxxxxxxx.job" (runxxxxx.bat)
>> Finished 06/10/2008 23:49:14
>> Result: The task completed with an exit code of (0).
>> "Caxxxxx.job" (Caxxxxx.sql)
>> Started 06/10/2008 23:50:00
>> Started indirectly, through a shortcut; task finish will not be logged.
>> "ZMFxxxxx.job" (zmfxxxxx.sql)
>> Started 06/10/2008 23:55:00
>> Started indirectly, through a shortcut; task finish will not be logged.
>> "runxxxxxC01.job" (runxxxxxxxxxxC01.bat)
>> Started 06/10/2008 23:59:00
>> "runZxxxxxxxx.job" (runxxxxxxxxxxxxx.bat)
>> Finished 06/10/2008 23:59:00
>> Result: The task completed with an exit code of (80).
>> "copxxxxxxx.job" (copyxxxxxxxx.bat)
>> Started 07/10/2008 19:55:00
>> "copyxxxxxx.job" (copyxxxxxxxx.bat)
>> Finished 07/10/2008 19:55:00
>> Result: The task completed with an exit code of (80).
>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>> Started 07/10/2008 20:05:00
>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>> Finished 07/10/2008 20:05:00
>> Result: The task completed with an exit code of (80).
>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>> Started 07/10/2008 20:10:00
>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>> Finished 07/10/2008 20:10:00
>> Result: The task completed with an exit code of (80).
>>
>> Thanks
>>
>> Paul

>
> Task Scheduler return codes are generated by the command you schedule, or
> by the last command in a batch file if it's a batch file you're
> scheduling. What exactly are you scheduling?
>
 
Re: Task Scheduler 0x80 errors

Fine. You now need to include some diagnostics in your batch file, e.g. like
so:
@echo off
echo. >> c:\test.txt
echo %date% %time% Start of batch job >> c:\test.txt
copy . . . 1>>c:\test.txt 2>>&
echo %time% Label 2 >> c:\test.txt
xcopy . . . 1>>c:\test.txt 2>>&
echo %time% Label 3 >> c:\test.txt
robocopy . . . 1>>c:\test.txt 2>>&
etc.

When the job fails, have a look at c:\test.txt. It will tell you what you
need to know.

"Paul" <chewbacca@wookie.org> wrote in message
news:uNqiuzRLJHA.4996@TK2MSFTNGP03.phx.gbl...
> It's various copy commands, batch files to copy out files and copy in a
> new blank file. After a reboot they work fine for abotu 7 days then fail
> with 0x80
>
>
> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
> news:e$rddviKJHA.5704@TK2MSFTNGP02.phx.gbl...
>>
>> "Paul" <chewbacca@wookie.org> wrote in message
>> news:Ouynw%23gKJHA.4908@TK2MSFTNGP02.phx.gbl...
>>> Hi,
>>>
>>> We have problems with scheduled tasks failing on windows 2000. A reboot
>>> solves this but we cannot get to the bottom of the problem. It's Sp4 and
>>> there's no Human Interface Devices service. I've tried making jobs with
>>> the
>>> AT command, assigning runas service and bath permissions and pretty much
>>> worked through a lot of search results. It seems to be about every 7
>>> days it
>>> fails. Can anyone shed light on this? There is nothing in event logs
>>> (app
>>> and system).
>>>
>>> Task log attached, job names aren't actually xxxxxxxxxx lol.
>>>
>>> "xxxxxxxxxx.job" (runxxxxx.bat)
>>> Started 06/10/2008 23:45:00
>>> "xxxxxxxxx.job" (runxxxxx.bat)
>>> Finished 06/10/2008 23:49:14
>>> Result: The task completed with an exit code of (0).
>>> "Caxxxxx.job" (Caxxxxx.sql)
>>> Started 06/10/2008 23:50:00
>>> Started indirectly, through a shortcut; task finish will not be logged.
>>> "ZMFxxxxx.job" (zmfxxxxx.sql)
>>> Started 06/10/2008 23:55:00
>>> Started indirectly, through a shortcut; task finish will not be logged.
>>> "runxxxxxC01.job" (runxxxxxxxxxxC01.bat)
>>> Started 06/10/2008 23:59:00
>>> "runZxxxxxxxx.job" (runxxxxxxxxxxxxx.bat)
>>> Finished 06/10/2008 23:59:00
>>> Result: The task completed with an exit code of (80).
>>> "copxxxxxxx.job" (copyxxxxxxxx.bat)
>>> Started 07/10/2008 19:55:00
>>> "copyxxxxxx.job" (copyxxxxxxxx.bat)
>>> Finished 07/10/2008 19:55:00
>>> Result: The task completed with an exit code of (80).
>>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>>> Started 07/10/2008 20:05:00
>>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>>> Finished 07/10/2008 20:05:00
>>> Result: The task completed with an exit code of (80).
>>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>>> Started 07/10/2008 20:10:00
>>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>>> Finished 07/10/2008 20:10:00
>>> Result: The task completed with an exit code of (80).
>>>
>>> Thanks
>>>
>>> Paul

>>
>> Task Scheduler return codes are generated by the command you schedule, or
>> by the last command in a batch file if it's a batch file you're
>> scheduling. What exactly are you scheduling?
>>

>
>
 
Re: Task Scheduler 0x80 errors

I've added this in, however it doesn't actually run the batch file as i had
a mkfile command to create a file as the first line in the batch job. I'll
monitor and see.

Thanks


"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:eTM7C8RLJHA.4324@TK2MSFTNGP05.phx.gbl...
> Fine. You now need to include some diagnostics in your batch file, e.g.
> like so:
> @echo off
> echo. >> c:\test.txt
> echo %date% %time% Start of batch job >> c:\test.txt
> copy . . . 1>>c:\test.txt 2>>&
> echo %time% Label 2 >> c:\test.txt
> xcopy . . . 1>>c:\test.txt 2>>&
> echo %time% Label 3 >> c:\test.txt
> robocopy . . . 1>>c:\test.txt 2>>&
> etc.
>
> When the job fails, have a look at c:\test.txt. It will tell you what you
> need to know.
>
> "Paul" <chewbacca@wookie.org> wrote in message
> news:uNqiuzRLJHA.4996@TK2MSFTNGP03.phx.gbl...
>> It's various copy commands, batch files to copy out files and copy in a
>> new blank file. After a reboot they work fine for abotu 7 days then fail
>> with 0x80
>>
>>
>> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
>> news:e$rddviKJHA.5704@TK2MSFTNGP02.phx.gbl...
>>>
>>> "Paul" <chewbacca@wookie.org> wrote in message
>>> news:Ouynw%23gKJHA.4908@TK2MSFTNGP02.phx.gbl...
>>>> Hi,
>>>>
>>>> We have problems with scheduled tasks failing on windows 2000. A reboot
>>>> solves this but we cannot get to the bottom of the problem. It's Sp4
>>>> and
>>>> there's no Human Interface Devices service. I've tried making jobs with
>>>> the
>>>> AT command, assigning runas service and bath permissions and pretty
>>>> much
>>>> worked through a lot of search results. It seems to be about every 7
>>>> days it
>>>> fails. Can anyone shed light on this? There is nothing in event logs
>>>> (app
>>>> and system).
>>>>
>>>> Task log attached, job names aren't actually xxxxxxxxxx lol.
>>>>
>>>> "xxxxxxxxxx.job" (runxxxxx.bat)
>>>> Started 06/10/2008 23:45:00
>>>> "xxxxxxxxx.job" (runxxxxx.bat)
>>>> Finished 06/10/2008 23:49:14
>>>> Result: The task completed with an exit code of (0).
>>>> "Caxxxxx.job" (Caxxxxx.sql)
>>>> Started 06/10/2008 23:50:00
>>>> Started indirectly, through a shortcut; task finish will not be logged.
>>>> "ZMFxxxxx.job" (zmfxxxxx.sql)
>>>> Started 06/10/2008 23:55:00
>>>> Started indirectly, through a shortcut; task finish will not be logged.
>>>> "runxxxxxC01.job" (runxxxxxxxxxxC01.bat)
>>>> Started 06/10/2008 23:59:00
>>>> "runZxxxxxxxx.job" (runxxxxxxxxxxxxx.bat)
>>>> Finished 06/10/2008 23:59:00
>>>> Result: The task completed with an exit code of (80).
>>>> "copxxxxxxx.job" (copyxxxxxxxx.bat)
>>>> Started 07/10/2008 19:55:00
>>>> "copyxxxxxx.job" (copyxxxxxxxx.bat)
>>>> Finished 07/10/2008 19:55:00
>>>> Result: The task completed with an exit code of (80).
>>>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>>>> Started 07/10/2008 20:05:00
>>>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>>>> Finished 07/10/2008 20:05:00
>>>> Result: The task completed with an exit code of (80).
>>>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>>>> Started 07/10/2008 20:10:00
>>>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>>>> Finished 07/10/2008 20:10:00
>>>> Result: The task completed with an exit code of (80).
>>>>
>>>> Thanks
>>>>
>>>> Paul
>>>
>>> Task Scheduler return codes are generated by the command you schedule,
>>> or by the last command in a batch file if it's a batch file you're
>>> scheduling. What exactly are you scheduling?
>>>

>>
>>

>
>
 
Re: Task Scheduler 0x80 errors

Also if I make a scheduled task to run calculator, it also fails with 0x80.


"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:eTM7C8RLJHA.4324@TK2MSFTNGP05.phx.gbl...
> Fine. You now need to include some diagnostics in your batch file, e.g.
> like so:
> @echo off
> echo. >> c:\test.txt
> echo %date% %time% Start of batch job >> c:\test.txt
> copy . . . 1>>c:\test.txt 2>>&
> echo %time% Label 2 >> c:\test.txt
> xcopy . . . 1>>c:\test.txt 2>>&
> echo %time% Label 3 >> c:\test.txt
> robocopy . . . 1>>c:\test.txt 2>>&
> etc.
>
> When the job fails, have a look at c:\test.txt. It will tell you what you
> need to know.
>
> "Paul" <chewbacca@wookie.org> wrote in message
> news:uNqiuzRLJHA.4996@TK2MSFTNGP03.phx.gbl...
>> It's various copy commands, batch files to copy out files and copy in a
>> new blank file. After a reboot they work fine for abotu 7 days then fail
>> with 0x80
>>
>>
>> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
>> news:e$rddviKJHA.5704@TK2MSFTNGP02.phx.gbl...
>>>
>>> "Paul" <chewbacca@wookie.org> wrote in message
>>> news:Ouynw%23gKJHA.4908@TK2MSFTNGP02.phx.gbl...
>>>> Hi,
>>>>
>>>> We have problems with scheduled tasks failing on windows 2000. A reboot
>>>> solves this but we cannot get to the bottom of the problem. It's Sp4
>>>> and
>>>> there's no Human Interface Devices service. I've tried making jobs with
>>>> the
>>>> AT command, assigning runas service and bath permissions and pretty
>>>> much
>>>> worked through a lot of search results. It seems to be about every 7
>>>> days it
>>>> fails. Can anyone shed light on this? There is nothing in event logs
>>>> (app
>>>> and system).
>>>>
>>>> Task log attached, job names aren't actually xxxxxxxxxx lol.
>>>>
>>>> "xxxxxxxxxx.job" (runxxxxx.bat)
>>>> Started 06/10/2008 23:45:00
>>>> "xxxxxxxxx.job" (runxxxxx.bat)
>>>> Finished 06/10/2008 23:49:14
>>>> Result: The task completed with an exit code of (0).
>>>> "Caxxxxx.job" (Caxxxxx.sql)
>>>> Started 06/10/2008 23:50:00
>>>> Started indirectly, through a shortcut; task finish will not be logged.
>>>> "ZMFxxxxx.job" (zmfxxxxx.sql)
>>>> Started 06/10/2008 23:55:00
>>>> Started indirectly, through a shortcut; task finish will not be logged.
>>>> "runxxxxxC01.job" (runxxxxxxxxxxC01.bat)
>>>> Started 06/10/2008 23:59:00
>>>> "runZxxxxxxxx.job" (runxxxxxxxxxxxxx.bat)
>>>> Finished 06/10/2008 23:59:00
>>>> Result: The task completed with an exit code of (80).
>>>> "copxxxxxxx.job" (copyxxxxxxxx.bat)
>>>> Started 07/10/2008 19:55:00
>>>> "copyxxxxxx.job" (copyxxxxxxxx.bat)
>>>> Finished 07/10/2008 19:55:00
>>>> Result: The task completed with an exit code of (80).
>>>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>>>> Started 07/10/2008 20:05:00
>>>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>>>> Finished 07/10/2008 20:05:00
>>>> Result: The task completed with an exit code of (80).
>>>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>>>> Started 07/10/2008 20:10:00
>>>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>>>> Finished 07/10/2008 20:10:00
>>>> Result: The task completed with an exit code of (80).
>>>>
>>>> Thanks
>>>>
>>>> Paul
>>>
>>> Task Scheduler return codes are generated by the command you schedule,
>>> or by the last command in a batch file if it's a batch file you're
>>> scheduling. What exactly are you scheduling?
>>>

>>
>>

>
>
 
Re: Task Scheduler 0x80 errors

Running calc.exe as a scheduled job is not very useful - you'll never know
whether it ran or not. Much better to run the first few lines of the batch
file I suggested:
@echo off
echo %date% %time% Start of batch job >> c:\test.txt
echo %UserName% %path% >> c:\test.txt

What account do you schedule the task under? Does it have a password?


"Paul" <chewbacca@wookie.org> wrote in message
news:%2337ZWoULJHA.5232@TK2MSFTNGP05.phx.gbl...
> Also if I make a scheduled task to run calculator, it also fails with
> 0x80.
>
>
> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
> news:eTM7C8RLJHA.4324@TK2MSFTNGP05.phx.gbl...
>> Fine. You now need to include some diagnostics in your batch file, e.g.
>> like so:
>> @echo off
>> echo. >> c:\test.txt
>> echo %date% %time% Start of batch job >> c:\test.txt
>> copy . . . 1>>c:\test.txt 2>>&
>> echo %time% Label 2 >> c:\test.txt
>> xcopy . . . 1>>c:\test.txt 2>>&
>> echo %time% Label 3 >> c:\test.txt
>> robocopy . . . 1>>c:\test.txt 2>>&
>> etc.
>>
>> When the job fails, have a look at c:\test.txt. It will tell you what you
>> need to know.
>>
>> "Paul" <chewbacca@wookie.org> wrote in message
>> news:uNqiuzRLJHA.4996@TK2MSFTNGP03.phx.gbl...
>>> It's various copy commands, batch files to copy out files and copy in a
>>> new blank file. After a reboot they work fine for abotu 7 days then fail
>>> with 0x80
>>>
>>>
>>> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
>>> news:e$rddviKJHA.5704@TK2MSFTNGP02.phx.gbl...
>>>>
>>>> "Paul" <chewbacca@wookie.org> wrote in message
>>>> news:Ouynw%23gKJHA.4908@TK2MSFTNGP02.phx.gbl...
>>>>> Hi,
>>>>>
>>>>> We have problems with scheduled tasks failing on windows 2000. A
>>>>> reboot
>>>>> solves this but we cannot get to the bottom of the problem. It's Sp4
>>>>> and
>>>>> there's no Human Interface Devices service. I've tried making jobs
>>>>> with the
>>>>> AT command, assigning runas service and bath permissions and pretty
>>>>> much
>>>>> worked through a lot of search results. It seems to be about every 7
>>>>> days it
>>>>> fails. Can anyone shed light on this? There is nothing in event logs
>>>>> (app
>>>>> and system).
>>>>>
>>>>> Task log attached, job names aren't actually xxxxxxxxxx lol.
>>>>>
>>>>> "xxxxxxxxxx.job" (runxxxxx.bat)
>>>>> Started 06/10/2008 23:45:00
>>>>> "xxxxxxxxx.job" (runxxxxx.bat)
>>>>> Finished 06/10/2008 23:49:14
>>>>> Result: The task completed with an exit code of (0).
>>>>> "Caxxxxx.job" (Caxxxxx.sql)
>>>>> Started 06/10/2008 23:50:00
>>>>> Started indirectly, through a shortcut; task finish will not be
>>>>> logged.
>>>>> "ZMFxxxxx.job" (zmfxxxxx.sql)
>>>>> Started 06/10/2008 23:55:00
>>>>> Started indirectly, through a shortcut; task finish will not be
>>>>> logged.
>>>>> "runxxxxxC01.job" (runxxxxxxxxxxC01.bat)
>>>>> Started 06/10/2008 23:59:00
>>>>> "runZxxxxxxxx.job" (runxxxxxxxxxxxxx.bat)
>>>>> Finished 06/10/2008 23:59:00
>>>>> Result: The task completed with an exit code of (80).
>>>>> "copxxxxxxx.job" (copyxxxxxxxx.bat)
>>>>> Started 07/10/2008 19:55:00
>>>>> "copyxxxxxx.job" (copyxxxxxxxx.bat)
>>>>> Finished 07/10/2008 19:55:00
>>>>> Result: The task completed with an exit code of (80).
>>>>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>>>>> Started 07/10/2008 20:05:00
>>>>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>>>>> Finished 07/10/2008 20:05:00
>>>>> Result: The task completed with an exit code of (80).
>>>>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>>>>> Started 07/10/2008 20:10:00
>>>>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>>>>> Finished 07/10/2008 20:10:00
>>>>> Result: The task completed with an exit code of (80).
>>>>>
>>>>> Thanks
>>>>>
>>>>> Paul
>>>>
>>>> Task Scheduler return codes are generated by the command you schedule,
>>>> or by the last command in a batch file if it's a batch file you're
>>>> scheduling. What exactly are you scheduling?
>>>>
>>>
>>>

>>
>>

>
>
 
Re: Task Scheduler 0x80 errors

I've done the >> C:\test.txt and will monitor this.

Yes the account has a password, however resetting it and doing so
accordingly in the scheduled task it still fails at 0x80. A reboot sorts it
every time though. Alas they wont accept that as a fix lol.



"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:OjjaDwULJHA.468@TK2MSFTNGP06.phx.gbl...
> Running calc.exe as a scheduled job is not very useful - you'll never know
> whether it ran or not. Much better to run the first few lines of the batch
> file I suggested:
> @echo off
> echo %date% %time% Start of batch job >> c:\test.txt
> echo %UserName% %path% >> c:\test.txt
>
> What account do you schedule the task under? Does it have a password?
>
>
> "Paul" <chewbacca@wookie.org> wrote in message
> news:%2337ZWoULJHA.5232@TK2MSFTNGP05.phx.gbl...
>> Also if I make a scheduled task to run calculator, it also fails with
>> 0x80.
>>
>>
>> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
>> news:eTM7C8RLJHA.4324@TK2MSFTNGP05.phx.gbl...
>>> Fine. You now need to include some diagnostics in your batch file, e.g.
>>> like so:
>>> @echo off
>>> echo. >> c:\test.txt
>>> echo %date% %time% Start of batch job >> c:\test.txt
>>> copy . . . 1>>c:\test.txt 2>>&
>>> echo %time% Label 2 >> c:\test.txt
>>> xcopy . . . 1>>c:\test.txt 2>>&
>>> echo %time% Label 3 >> c:\test.txt
>>> robocopy . . . 1>>c:\test.txt 2>>&
>>> etc.
>>>
>>> When the job fails, have a look at c:\test.txt. It will tell you what
>>> you need to know.
>>>
>>> "Paul" <chewbacca@wookie.org> wrote in message
>>> news:uNqiuzRLJHA.4996@TK2MSFTNGP03.phx.gbl...
>>>> It's various copy commands, batch files to copy out files and copy in a
>>>> new blank file. After a reboot they work fine for abotu 7 days then
>>>> fail with 0x80
>>>>
>>>>
>>>> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
>>>> news:e$rddviKJHA.5704@TK2MSFTNGP02.phx.gbl...
>>>>>
>>>>> "Paul" <chewbacca@wookie.org> wrote in message
>>>>> news:Ouynw%23gKJHA.4908@TK2MSFTNGP02.phx.gbl...
>>>>>> Hi,
>>>>>>
>>>>>> We have problems with scheduled tasks failing on windows 2000. A
>>>>>> reboot
>>>>>> solves this but we cannot get to the bottom of the problem. It's Sp4
>>>>>> and
>>>>>> there's no Human Interface Devices service. I've tried making jobs
>>>>>> with the
>>>>>> AT command, assigning runas service and bath permissions and pretty
>>>>>> much
>>>>>> worked through a lot of search results. It seems to be about every 7
>>>>>> days it
>>>>>> fails. Can anyone shed light on this? There is nothing in event logs
>>>>>> (app
>>>>>> and system).
>>>>>>
>>>>>> Task log attached, job names aren't actually xxxxxxxxxx lol.
>>>>>>
>>>>>> "xxxxxxxxxx.job" (runxxxxx.bat)
>>>>>> Started 06/10/2008 23:45:00
>>>>>> "xxxxxxxxx.job" (runxxxxx.bat)
>>>>>> Finished 06/10/2008 23:49:14
>>>>>> Result: The task completed with an exit code of (0).
>>>>>> "Caxxxxx.job" (Caxxxxx.sql)
>>>>>> Started 06/10/2008 23:50:00
>>>>>> Started indirectly, through a shortcut; task finish will not be
>>>>>> logged.
>>>>>> "ZMFxxxxx.job" (zmfxxxxx.sql)
>>>>>> Started 06/10/2008 23:55:00
>>>>>> Started indirectly, through a shortcut; task finish will not be
>>>>>> logged.
>>>>>> "runxxxxxC01.job" (runxxxxxxxxxxC01.bat)
>>>>>> Started 06/10/2008 23:59:00
>>>>>> "runZxxxxxxxx.job" (runxxxxxxxxxxxxx.bat)
>>>>>> Finished 06/10/2008 23:59:00
>>>>>> Result: The task completed with an exit code of (80).
>>>>>> "copxxxxxxx.job" (copyxxxxxxxx.bat)
>>>>>> Started 07/10/2008 19:55:00
>>>>>> "copyxxxxxx.job" (copyxxxxxxxx.bat)
>>>>>> Finished 07/10/2008 19:55:00
>>>>>> Result: The task completed with an exit code of (80).
>>>>>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>>>>>> Started 07/10/2008 20:05:00
>>>>>> "Artixxxxxxxxxxxxx.job" (backstart.bat)
>>>>>> Finished 07/10/2008 20:05:00
>>>>>> Result: The task completed with an exit code of (80).
>>>>>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>>>>>> Started 07/10/2008 20:10:00
>>>>>> "runZOpxxxxxxxxx.job" (runZOpxxxxxxxxxx.bat)
>>>>>> Finished 07/10/2008 20:10:00
>>>>>> Result: The task completed with an exit code of (80).
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Paul
>>>>>
>>>>> Task Scheduler return codes are generated by the command you schedule,
>>>>> or by the last command in a batch file if it's a batch file you're
>>>>> scheduling. What exactly are you scheduling?
>>>>>
>>>>
>>>>
>>>
>>>

>>
>>

>
>
 
Re: Task Scheduler 0x80 errors

I believe the 0x80 = ERROR_WAIT_NO_CHILDREN

This article may prove useful.

http://support.microsoft.com/kb/184802



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"Paul" wrote:
> I've done the >> C:\test.txt and will monitor this.
>
> Yes the account has a password, however resetting it and doing so
> accordingly in the scheduled task it still fails at 0x80. A reboot sorts
> it every time though. Alas they wont accept that as a fix lol.
 
Back
Top