May 4, 2009 at 2:06 pm
Weird one here...
Due to some conflicts on the network between DPM and some Index Rebuilds I have a couple of Jobs that were scheduled to run shortyly after midnite on Saturday that failed to complete but instead of ending are showing up as In Progress/Running when viewing the Log File Viewer.
Since the job failed the SQL Server has been hard re-booted so I know for a fact there's no way the job is still running. I've also restarted the SQL Agent and the same 4 process that show in Activity Monitor are still showing up after the restart.
Any thoughts on this? Anything I can do to get the job to show with the proper status in the Log Viewer?
Kindest Regards,
Just say No to Facebook!March 15, 2010 at 2:42 pm
Hi there, did you get any resolution ?
I have a problem where I came in from the weekend to find the jobs still running.
I stopped the SQL Agent and then I restarted the server as windows updates had been applied, thinking that the restart would help.
Today the jobs in the SQL Agent window say they are not running but the Log File viewer says they are running.
How can I reset these jobs in the MSDB database to show that they have completed.
I tried this query posted on another site and it shows that the step ID for my job is 1 not 0, how do I reset it to show that it is complete.
exec msdb.dbo.sp_help_jobhistory @job_id = 'your-job-guid-here', @mode='FULL'
Any ideas are greatly appreciated.
Cheers
Angie
March 15, 2010 at 4:08 pm
Sorry but no, not yet.
Kindest Regards,
Just say No to Facebook!Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply