SQL Server Agent runs jobs out of schedule

• TommyF

  Old Hand

  Points: 332

  More actions

  July 6, 2014 at 9:05 am

  #397013

  Hi,

  We have hundreds of concurrent running jobs.

  Each day some jobs (different ones) run in times when they are not scheduled.

  Please see data from yesterday. I just can't explain the second row:

  The job succeeded. The Job was invoked by Schedule 4107 (Schedule1). The last step to run was step 4. 20140705 190447

  The job succeeded. The Job was invoked by User PROD\SQLAgentUser. The last step to run was step 4. 20140705 190021

  The job succeeded. The Job was invoked by Schedule 4107 (Schedule1). The last step to run was step 4. 20140705 190001

  The job succeeded. The Job was invoked by Schedule 4107 (Schedule1). The last step to run was step 4. 20140705 184938

  The job succeeded. The Job was invoked by Schedule 4107 (Schedule1). The last step to run was step 4. 20140705 184518

  The job succeeded. The Job was invoked by Schedule 4107 (Schedule1). The last step to run was step 4. 20140705 184010

  There is no way that someone runs the jobs manually since when it happens there are 10-15 jobs that

  suddenly start unexpected.

  Thanks,

  Tommy.

• TommyF

  Old Hand

  Points: 332

  More actions

  July 6, 2014 at 11:00 pm

  #1727264

  We found the problem. It's a "fixer" job that start the other ones.

  Sorry for wasting your time and for blaming SQL Server Agent 🙂