Run Dtsx as SQL Agent Task

[Peter Newman]

WIndows SQL2008 & Windows 2008R2

I opened a 2005 dtsx in BIDS ( 2008 ) and after a few sdjustments it runs
fine. The dtsx imports data from a flat file a UNC drive, then moves it to
another drive. I am signed onto WindowsR2 as Domain\SQLManager. SQLManager
has access to the unc drives for read / write/ create and delete. When
setting a SQL Agent job to run this task, it reports back sucessful with no
errors, but no files are moved and no data imported. The service for the SQL
agant is bought is run as SQL Manager. I cannot figure out why the dtsx wont
run correctly as a SQL task. Can anyone help?

[Todd C]

Possible the package is running as it should but either could not reach the
steps or had the wrong file name.

Is there any kind of logic in your package that could cause the runtime
engine to bypass the Data Flow and File System tasks? Like a Sequence
Container or ForEach loop perhaps?
Is the File name of the flat file hard-coded in the package, or does it
change each time, and if so, how does the package know the new name?
--
Todd C
MCTS SQL Server 2005

Post by Peter Newman
WIndows SQL2008 & Windows 2008R2
I opened a 2005 dtsx in BIDS ( 2008 ) and after a few sdjustments it runs
fine. The dtsx imports data from a flat file a UNC drive, then moves it to
another drive. I am signed onto WindowsR2 as Domain\SQLManager. SQLManager
has access to the unc drives for read / write/ create and delete. When
setting a SQL Agent job to run this task, it reports back sucessful with no
errors, but no files are moved and no data imported. The service for the SQL
agant is bought is run as SQL Manager. I cannot figure out why the dtsx wont
run correctly as a SQL task. Can anyone help?