March 19, 2008 at 2:03 pm
Scenario:
I have a DTS package scheduled. On server "A". When the job runs successfully, an entry is inserted into msdb.SysJobHistory.
HOWEVER, when the job fails, no record is being written to SysJobHistory!
I cannot figure out why. I have this problem on more than one server...some of the servers insert a run_status = 0 into SysJobHistory when the job fails and some do not add a record at all.
Thus, I do not have ANY history of job failures on the problematic server.
SQL newbie here...any suggestions or advice is greatly appreciated! (log files are not full...I even cleared the SysJobHistory to see the problem "naked")...
March 21, 2008 at 7:53 am
I would like to recommend you to add a log file to your DTS package in order to find errors in detail.
March 21, 2008 at 10:08 am
How do you know that it "failed"? Maybe it is still running or is hung? Or maybe it it exited without an error, but not when or where you expected it to?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 24, 2008 at 7:48 am
Thank you both for your replies. I know the job failed because it listed in Enterprise manager with a last run status as failed and the nice red "x" icon.
Another developer was the source of my problem... a trigger on sysjobhistory (very bad idea, I know) was bad/rogue/causing a hang up, thus the erroring packages were not being recorded!
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply