Hello,

I am currently in the initial planning stages for a large project that
will be using DTS extensively. I would like to come up with a simple
and consistent error logging method that we can use. My first thought
is to use a simple table that stores errors (description, date & time,
where the error occurred, etc.).

In our stored procedures this is easy enough to support. I have an
insert stored procedure that saves the error information and it is easy
to call this within another stored procedure. In trying to use this
same approach in DTS I am having some trouble though. It seems a little
cumbersome since the developer would have to set global variables any
time that they hit an error. This means writing VB Script after every
task just to set the global variables so that they can be passed to a
child package or used to call a stored procedure.

I tried creating a single script that could handle this, but
GetExecutionErrorInfo isn't available from VB Script, so I'm not sure
how to generically handle it. Anything that I've found on the web or in
the newsgroups just mentions turning on DTS' intrinsic error handling.
This is nice, but I'd like to have all of our errors in one place for
consistency.

I anticipate similar problems with our process auditing, so any ideas
there would be welcome as well. For process auditing it would be as
simple as tracking start and end times for parts of the processes along
with return codes. Something that allows the continuation of a process
that errored out earlier would be great, but not necessary yet.

Can anyone point me to a document that explains a custom error handling
approach (and/or process auditing) in DTS?

Thanks,
-Tom.