Job monitoring - time problems and agent not running

• 
  Currently, I have a problem with the monitor logging "Job Did Not Start" for future jobs. These jobs are not scheduled to run until this evening but are getting logged as "Job Did Not Start" in the morning. This is annoying given that this accounts for the majority of the incidents and when it happens in the evening and I don't see it until after the time the job runs it proves to be completly inaccurate.
  
  I suggest that you work off of a 24hr time to avoid confusion in reading the log, given this issue.

  EnigmaGuru February 08, 2008 14:22

  - 0 +
• 

  sgreene wrote:

  I'm getting incidents for jobs that are running successfully. It says the job did not start(agent not running). My Agent is running. The time stamp for the incident is also off. The latest incident is 11:58PM on 2/8/2008. It's only 9:14AM where I'm at.
  
  Sam

  
  Is the time on the server different (i.e. different timezone)? The incidents are reported as the server time rather than your local time.

  Nigel Morse February 11, 2008 04:28

  - 0 +
• 

  EnigmaGuru wrote:

  Currently, I have a problem with the monitor logging "Job Did Not Start" for future jobs. These jobs are not scheduled to run until this evening but are getting logged as "Job Did Not Start" in the morning. This is annoying given that this accounts for the majority of the incidents and when it happens in the evening and I don't see it until after the time the job runs it proves to be completly inaccurate.
  
  I suggest that you work off of a 24hr time to avoid confusion in reading the log, given this issue.

  
  
  The times are read as 24hour format so we'll have to take a look at why those future failures are comming up. Thanks for reporting it.

  Nigel Morse February 11, 2008 04:29

  - 0 +
• 
  Hi Enigma,
  

  EnigmaGuru wrote:

  Currently, I have a problem with the monitor logging "Job Did Not Start" for future jobs. These jobs are not scheduled to run until this evening but are getting logged as "Job Did Not Start" in the morning. This is annoying given that this accounts for the majority of the incidents and when it happens in the evening and I don't see it until after the time the job runs it proves to be completly inaccurate.

  
  Could you run the following query for us please, and forward the results to my email address ( jason.cook@red-gate.com ). The query returns the list of schedules for the specified job (whose name you need to insert in the <jobname> bit), and should help us to diagnose why the incident repository is calculating the next run date incorrectly.
  

  exec msdb..sp_help_jobschedule @job_name = '<jobname>';
  

  
  Thanks,
  Jason

  Jason Cook February 11, 2008 06:04

  - 0 +
• 

  Nigel Morse wrote:

  sgreene wrote:

  I'm getting incidents for jobs that are running successfully. It says the job did not start(agent not running). My Agent is running. The time stamp for the incident is also off. The latest incident is 11:58PM on 2/8/2008. It's only 9:14AM where I'm at.
  
  Sam

  
  Is the time on the server different (i.e. different timezone)? The incidents are reported as the server time rather than your local time.

  
  The servers are all in the US mountain time zone, but we are in Arizona and don't observe daylight savings.

  sgreene February 12, 2008 12:01

  - 0 +
• 

  sgreene wrote:

  The servers are all in the US mountain time zone, but we are in Arizona and don't observe daylight savings.

  
  So that should only be an hour or two difference then. Could you check what time SQL Server reports when you run:

  select getdate();
  

  
  Thanks

  Nigel Morse February 12, 2008 12:08

  - 0 +

Add comment

Please sign in to leave a comment.