August 30, 2005 at 6:09 am
We have a job step that fails every now and then. When viewing the step details in the job history the message length is not sufficient to capture the actual error. The procedure outputs status information that essentially consumes the full message length before the error is encountered. The only difference we see between a successful run and a failed run is that the end of the message has "... The step succeeded" instead of "... The step failed".
We run these systems for our customer so we don't have any leeway as far as moifying their code. I was hoping that there was some way to increase the message length, or identify where the full message might be stored, in the hopes of identifying the actual error. I thought that perhaps the SQL Agent log would have captured the information, but no luck there.
Any ideas would be greatly appreciated.
Thanks
Will
August 30, 2005 at 10:57 am
I usually write each job step out to a text file. It tends to have more useful information & doesn't get truncated.
Open the job, then go to each step, then the Advanced tab, then put in a path and output file name.
September 1, 2005 at 3:00 am
Hi,
In the sysjobs of msdb database there is a field named messages can increase the length.
the error messeges are written in the windows error log.
hope this helps u.
from
killer
September 1, 2005 at 5:17 am
Homebrew01 and Journeyman -
Thanks for your feedback. Since I am reluctant to modify system tables, I output the job step output to a log file which suits our needs just fine.
Will
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply