Build 520 - erroneous "Job did not start" persists

• 
  Hi,
  Is the date correct at least now? the problem before was the date of the Job Did Not Start was in the future - I just want to see if this is the same or a new problem.
  
  What we so is to check is the last run date of the job, which if it's showing in the job history then it should have updated.
  
  If you're using Enterprise Manager then when you show the jobs it should have a "last run status (Start Date)" column - which should show when this job last ran and whether it worked or not (this is different from the job history.) Could you possibly check this soon after a "did not start" incident arrives and possibly send me screen shots of that and of SQL Response please?
  
  Thanks,
  Nigel

  Nigel Morse February 26, 2008 05:26

  - 0 +
• 
  The Job is correctly shown as "today".
  
  When I looked the job up in Job Monitor under VSMS, it was successful on ALL occasions, with ALL steps having run (Job has only 1 step).
  
  Screenshots emailed...
  
  I found that the Transaction Log backup job, also signalled as "Job did not start", ran for 2 seconds ("Duration" column on the Job Monitor).

  PDinCA February 26, 2008 14:15

  - 0 +
• 
  Incident type: Job did not start
  Subject: <Job name is here>
  Incident Time: 2/28/2008 8:05:00 AM
  SQL Server <server name is here>
  
  Job name: <Job name is here>
  Description: <description of job is here>
  Category: [Uncategorized (Local)]
  Owner: <owner name is here>
  
  Run <batch name is here>
  Step name: <step name is here>
  Subsystem: TSQL
  Run Status: Succeeded
  
  Command: <sproc name is here>
  
  Additional Information:
  Executed as user: <user name is here> The step succeeded.
  
  DateTime is correct.
  Kind of peculiar, it knows the job succeeded, but reports that it didn't start.
  (Beta anyway, but this is the point of posting the confirmation, hope this helps in some way.)

  randyv February 28, 2008 08:33

  - 0 +
• 
  I also received a "job did not start" error when in fact it did execute successfully. The job execution duration was 00:00:00. For this quick running job that is normal, but I only get a "did not start error" occasionally.

  redrazorback March 03, 2008 16:35

  - 0 +

Add comment

Please sign in to leave a comment.