DTS Package

Hello everyone,
I am wondering if anyone can shed any light on a DTS issue that I am
facing. At my company we are using multiple DTS packages to extract
data from a 3rd party database using their ODBC driver. Every so often
a couple of the DTS packages fail - which can prove to be a real pain -
as I and a colleague have to check these processes around 7am every
morning (becuase some of the packages can take an hour + to complete)
to ensure that they have all worked as expected.
Now, when a DTS package fails I am sent an e-mail notification from
SQLServer.
E.g.
JOB RUN: 'PurchaseControl' was run on 07/06/2006 at 06:00:00
DURATION: 0 hours, 7 minutes, 46 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by Schedule 64
(PurchaseControl). The last step to run was step 1 (PurchaseControl).
This is OK as it tells me the package that fails. However, I cannot see
why it failed, there is no runtime information regarding the error that
occured. Now, if I run a DTS package manually through SQL Server 2000
Enterprise Manager and a step in the DTS package fails it tells me
why...
E.g.
[Kerridge][KISAM ODBC Driver]error reading pkt body
Is it possible to obtain this type of information from scheduled DTS
packages, so that I can examine what are the common problems within the
packages?
I'd really, really appreciate help on this one, if anyone can spare the
time.
Thanks in advance,
Craig.Hi Craig,
Yes, within the package properties you have a logging tab where you can set
the package to an error file.
Ray
"crgsmrt@.googlemail.com" wrote:

> Hello everyone,
> I am wondering if anyone can shed any light on a DTS issue that I am
> facing. At my company we are using multiple DTS packages to extract
> data from a 3rd party database using their ODBC driver. Every so often
> a couple of the DTS packages fail - which can prove to be a real pain -
> as I and a colleague have to check these processes around 7am every
> morning (becuase some of the packages can take an hour + to complete)
> to ensure that they have all worked as expected.
> Now, when a DTS package fails I am sent an e-mail notification from
> SQLServer.
> E.g.
> JOB RUN: 'PurchaseControl' was run on 07/06/2006 at 06:00:00
> DURATION: 0 hours, 7 minutes, 46 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 64
> (PurchaseControl). The last step to run was step 1 (PurchaseControl).
>
> This is OK as it tells me the package that fails. However, I cannot see
> why it failed, there is no runtime information regarding the error that
> occured. Now, if I run a DTS package manually through SQL Server 2000
> Enterprise Manager and a step in the DTS package fails it tells me
> why...
> E.g.
> [Kerridge][KISAM ODBC Driver]error reading pkt body
> Is it possible to obtain this type of information from scheduled DTS
> packages, so that I can examine what are the common problems within the
> packages?
> I'd really, really appreciate help on this one, if anyone can spare the
> time.
> Thanks in advance,
> Craig.
>|||rb wrote:
> Hi Craig,
> Yes, within the package properties you have a logging tab where you can se
t
> the package to an error file.
> Ray
> "crgsmrt@.googlemail.com" wrote:
>
Hi Ray,
Thanks for that. However, I cannot appear to locate this 'logging tab'.
Would you mind telling me where to locate it. The closest item I have
found is on the 'Notifications' tab in the Management>>Jobs section.
However, I do not believe this is what you are referring to.
Regards,
Craig.|||rb wrote:
> Hi Craig,
> Yes, within the package properties you have a logging tab where you can se
t
> the package to an error file.
> Ray
> "crgsmrt@.googlemail.com" wrote:
>
The information that gets dumped into the Event Log is just as useless
too...
SQL Server Scheduled Job 'PointOfSale'
(0xE2A9D65E6F5BB04C9C6116CE1F07AA65) - Status: Failed - Invoked on:
2006-06-06 03:00:02 - Message: The job failed. The Job was invoked by
Schedule 61 (PointOfSale). The last step to run was step 1
(PointOfSale).|||Thanks Ray,
I've found it already.
Craig.
rb wrote:
> Hi Craig,
> Yes, within the package properties you have a logging tab where you can se
t
> the package to an error file.
> Ray
> "crgsmrt@.googlemail.com" wrote:
>