Strange problem guys. I need the help of an expert to
solve this.

This is for SQLserver 2000 only. with latest service pack.

The DTS package execute by itself just fine. But when its
scheduled it fails with the following error message.


" Executed as user: Server1\Administrator. ...QL Server
Objects DTSRun OnProgress: Copy SQL Server Objects;
Scripting objects for Transfer; PercentComplete = 0;
ProgressCount = 0 DTSRun OnError: Copy SQL Server
Objects, Error = -2147024893 (80070003) Error
string: The system cannot find the path
specified. Error source: Microsoft Data
Transformation Services (DTS) Package Help file:
sqldts80.hlp Help context: 1100 Error Detail
Records: Error: -2147024893 (80070003); Provider
Error: 0 (0) Error string: The system cannot find
the path specified. Error source: Microsoft Data
Transformation Services (DTS) Package Help file:
sqldts80.hlp Help context: 1100 Error: -
2147024893 (80070003); Provider Error: 0 (0) Error
string: The system cannot find the path
specified. Error source: Microsoft Data
Transformation Services (DTS) Package Help file:
sqldts80.hlp Help... Process Exit Code 1. The step
failed."

The administartor has full rights and is the owner of the
Job and the dts pacakage and also it is the owner for
SQL agent service and Sql starup account.

I have followed the following instruction but of no avail

http://support.microsoft.com/?kbid=322746

http://support.microsoft.com/default.aspx?scid=kb;EN-
US;269074

I have complely looked at each and every aspect. Please
advice.

WHen a package is scheduled, the package is run under the account that SQL
Server Agent runs under, whereas when you run it manually, it runs under the
account logged in at the time.

I would recommend turning on package logging if it is not already, determine
which step in the package fails, and check to see if this makes any
references to local drives or mapped network drive letters, which may not be
available to both users. It might be a path in a connection or a reference
in a Active X Script.

If so, this is easily overcome by using UNC paths for all file references
\\Server\share\filename

Regards

ROB

"Jimmy" <anonymous (AT) discussions (DOT) microsoft.com> wrote

please disregard my last posting. I missed the bottom of your description of
the problem.

ROB


"Rob Zalisz" <robz (AT) worxdesign (DOT) com> wrote