When you run the package by hand are you at the server (whether physically
or using a terminal server session) or at your PC? Where you run it is where
it runs. So if you run it on your PC and you specify a local path of
C:\DTSData\transfer.xls then it will look on your PC. If you specify a UNC
path \\Server\Share\Transfer.xls then that is where it will look. When you
run by hand it will use your windows credentials to connect to the share.
When you run it as a job step then it will run as the SQL Server Agent
account (if you are a sysadmin, if not then it uses the cmdexec proxy
account). If the SQL Server Agent account is local system then accessing the
UNC path (even though it really points to the local system) it will fail. If
you are using a local path make certain that is exists on the server
--
David Lundell
Principal Consultant and Trainer
www.MutuallyBeneficial.com
David (AT) MutuallyBeneficial (DOT) com
"Travis" <Travis (AT) discussions (DOT) microsoft.com> wrote
Quote:
Hi ,
I created a package in SQL Server and use VB6 to run the package. This
package consist of a file transfer (excel) from local server C:\ drive and
load the data into the database. It looks well when I run manually.
When I run the package in VB on my PC , the package failed to run. The
error msg are :
Step "DTSStep - Transfer Source Tmp" Failed
Error: -2147467259
Source: Microsoft JET Database Engine
Description: Failure creating file.
I am suspecting the package looking the files on the PC not on server.
How
to let the package know it should pick up the files from server itself ?
Many Thanks ..
Travis
--
Travis Tan |