Agent Jobs fail in time frame

  • Hello,
    My SQL Server Agent does not process any of my jobs between 12am and 2am.  The job runs for about 30 seconds then it fails.  The error is described as follows:

    ...failed to execute is server package because of error 0x80131904...  The timeout period elapsed prior to completion of the operation or the server is not responding...

    Some solutions so far mention to increase the time-out from 30, or to speed up the queries in jobs.  Thank you in advance for your help.

  • Is there a backup running at that time?

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

  • Phil Parkin - Saturday, February 24, 2018 1:09 PM

    Is there a backup running at that time?

    yes, but it's between 12:20 and 12:40.  some jobs that run at 12 fail and some jobs that run at 1:30 fail, which is before, during and after backup

  • The quick and dirty solution is to increase to number of attempts (i.e. 0 to 3).  (Job Properties, Steps, Advanced Options)  Does anyone know why it can't just process at the first attempt, like all the other jobs?

  • If it's not the backup, there's probably something else running that's preventing a timely connection. One option you might try is creating a new job to run the package and see if that succeeds during the time frame.

  • clicky - Saturday, February 24, 2018 11:28 AM

    Hello,
    My SQL Server Agent does not process any of my jobs between 12am and 2am.  The job runs for about 30 seconds then it fails.  The error is described as follows:

    ...failed to execute is server package because of error 0x80131904...  The timeout period elapsed prior to completion of the operation or the server is not responding...

    Some solutions so far mention to increase the time-out from 30, or to speed up the queries in jobs.  Thank you in advance for your help.

    What the job\package does?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply