Hi everyone:

I've a question that I can't seem to find an answer on so I figured I'd
see if it can even be done.

We have several DTS packages that are run on schedule through several
jobs. Is there a way in job step to get the error message from a
previous job step that failed short of querying the job history table?

The reason I ask is that we have a SQL Server running on a machine and
SQL Mail is not running on it so I can't use the automated
notifications built into the job steps. I have a stored procedure that
will let me send an email via SMTP and would like to have any failed
steps in a job go to the last step that executes the stored procedure
to send the email. What I need is to be able to get the error message
that caused the failure.

The only other way I can think of doing this is to write the steps to a
log file then email the log file as an attachment.

One other possibilty would be to use an alert that is triggered when a
job fails, that way I could having to add a step to all of the jobs.
The alert could then run a job but the problem remains of trying to
determine the reason for the error.

Any help, input, or other suggestions would be greatly appreciated.

Another option is to use an output file for your job steps.
When the set fails and executes the smtp step, attach a copy
of the output file to the email.

-Sue

On 16 Mar 2006 15:51:29 -0800, dsvick (AT) gmail (DOT) com wrote: