NOTE: Operator ''XXX'' is not currently on duty so cannot be paged.

• Leeland

  SSCrazy Eights

  Points: 8959

  More actions

  January 4, 2007 at 8:05 am

  #62113

  Had a job failure due to xp_sendmail failure within a job step. I had the job set up to page me when the job fails via an operator. Came in this morning and realized I had not gotten paged...in the job history it had the following notation

  NOTE: Operator 'GentranNotification' is not currently on duty so cannot be paged.

  The operator works now (did a test page and email). I tried to Google the error message but did not find anything that I felt explained what this means.

  I looked in the Error and SQL Server Logs and didn't find anything either...

  If anyone has some information that they would like to share I would appreciate it.

  Thanks,

  Leeland

• Rich Hansell

  SSCrazy

  Points: 2346

  More actions

  January 4, 2007 at 9:24 am

  #681247

  Did you confirm in the operator properties that the 'GentranNotification' operator doesn;t have a schedule set?

• Leeland

  SSCrazy Eights

  Points: 8959

  More actions

  January 4, 2007 at 9:28 am

  #681250

  EDIT: OK either someone changed it, saw the error and then changed it back before I got in or I am a complete dumb a$$ and set the schedule wrong myself.

  When I got in the schedule was set as below...however when the error happened, the work end was set for 5 p.m., which is stupid because the job runs at 7 p.m.

  Probably me not paying attention...so no problem here, just move along

  It does have a schedule, everyday is enabled and the start time is 12:00 A.M. and the workday end is 11:59 p.m.

  If I disable all the days would that be the same as having the operator on at all times?

  Thanks for the input.

  Leeland