DTSRUN Batch FIle not writing to disk

> Is anyone aware of any security related issue/feature with DTSRUN
> which prevents child processes from accessing certain resources.

There are a few differences between running a package interactively vs. from
a scheduled job. When run as a job, the package runs on the SQL Server
machine and under the security context of the SQL Agent account (or SQL
Agent proxy account if not owned by sa). When run from Enterprise Manager,
the package runs under the security context of the invoking user and it runs
on the same machine as EM. This can either a remote PC or the SQL Server
box.

Where the package runs is important because file paths are relative to that
location.

--
Hope this helps.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

wrote in message
news:b5fffadb-846d-483f-88d6-8fc3d3797493@z72g2000hsb.googlegroups.com...
> Hi
>
> I have inherited a system that has a series of DTS packages that are
> run sequentially as a scheduled job. The 1st step run a batch file,
> which in turn runs a small java application which writes a number of
> CSV files which are used by later packages.
>
> The problem is that the package runs fine, but the output from the
> java application is not written to disk. No errors are generated. If
> the package is executed from design view it works fine.
>
> Ihave monitored the processes, and when scheduled DTSRUN is executed
> with the package name, therefore you get a process tree of
>
> DTSRUN.EXE > CMD.EXE > JAVA.EXE
>
> When run from the designer you get:
>
> CMD.EXE > JAVA.EXE
>
> Is anyone aware of any security related issue/feature with DTSRUN
> which prevents child processes from accessing certain resources.
>
> Any help would be greatly appreciated.
>
> TIA
>
> SHaun Laughton