scheduler exit code 0x80

Discussion in 'Windows Server' started by TPGBrennan, Jun 3, 2010.

  1. TPGBrennan

    TPGBrennan Guest

    I have a Windows 2003 R2 SP2 x64 Enterprise Edition server that has
    successfully run six scheduled tasks for more than a year. All of the tasks
    fail as of this morning with an exit code of 0x80. The tasks run under
    different service accounts and run different tasks including batch files,
    powershell scripts and a third party app. All of them have the same problem.
    The only information in the scheduler log is the exit code of 0x80, there is
    nothing in any of the event logs. The problem developed between a successful
    task last night at 2100 and the first morning task failing at 0730. No
    changes have been made to the server during that time.

    Does anyone have any clue what an exit code of 0x80 means?
    TPGBrennan, Jun 3, 2010
    1. Advertisements

  2. TPGBrennan

    Dave Patrick Guest

    Dave Patrick, Jun 3, 2010
    1. Advertisements

  3. TPGBrennan

    TPGBrennan Guest

    I'm still not sure what an exit code of 0x80 means but I figured out what my
    specific problem was. The third party app running as a scheduled task had
    spawned 68 child processes in the last month and never closed them down. I
    killed all the child processes and the parent and scheduler works fine again.
    Apparently, scheduler couldn't start anything after a certain point; the
    last of the 68 children was spawned in the time window the scheduler stopped
    working. this would explain some of the posts I have found that said a
    reboot resolved the issue for a while and then it would come back. We
    usually reboot the server each month for MS patching but could not last month
    because of a configuration lockdown. i will monitoring the errant task going

    My server and tasks didn't meet any of the conditions mentioned the KB
    article referenced.

    TPGBrennan, Jun 3, 2010
  4. TPGBrennan

    Dave Patrick Guest

    Might need a delayed cleanup / kill task if the problem can't be fixed.



    Dave Patrick ....Please no email replies - reply in newsgroup.
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Dave Patrick, Jun 3, 2010
  5. TPGBrennan

    Nick Allen Guest

    In my case, I went into Terminal Services Manager and reset a disconnected session and then the scheduled ran fine in the current RDP session.

    Never seen that before.


    Nick Allen, Sep 28, 2010
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.