November 1, 2007 at 12:14 pm
SQL Server 2000 SP3a - Standard Edition - Windows Server 2003
I have a non-existent job that is posting a failure in the Windows Event Log and sending notifications via the enabled operators that I have in the SQL Agent.
Error Message from the Event Log:
"SQL Server Scheduled Job 'db_job_full_backup' (0x41CF3E643C108F4CA0218A2B5A6D16FF) - Status: Failed - Invoked on: 2007-11-01 01:00:00 - Message: The job failed. Unable to retrieve steps for job db_job_full_backup.
I have a job by the same name that is running successfully, but that runs at 00:01. If you look at the job in the SQL Agent jobs view, it says that it ran successfully, and the history shows no failure on any steps.
To give a little history, I recently changed the job via SQL Script. The way that I changed it was to delete the job in it's entirety and then recreate the job. I used sp_delete_job to delete the job that had been running at 01:00 and created a new job to run at 00:00. (This, of course was not the only change or I would have just adjusted the schedule.)
I have looked in the sysjobs, sysjobschedules, sysjobservers, sysjobhistory, and sysjobsteps tables. I can only see the current job. I see no reference to the old job.
The failure does not show up in the SQL Server Logs.
Any ideas where I may be failing to look?
November 19, 2007 at 8:54 am
Is this still happening? Any resolution?
Could it be scheduled twice?
November 19, 2007 at 9:25 am
Sorry, had this posted in two different places, but forgot to post the resolution, here.
These 'phantom jobs' were evidently being held in cache. I stopped and restarted the SQL Server Agent, and these problems ceased.
Thanks, Steve
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply