I'm trying to schedule a DTS package that generates a flat file and then
does an SFTP upload of that file. The package runs a batch file (using an
execute process task) to do the upload. The batch file contains commands
for an SFTP command line program (exe file) to do the upload. When I run
the package from Enterprise Manager it runs fine, but when I schedule the
package, it hangs during execution. I've tried 2 different SFTP software
packages to do the upload, so it does not appear to be a problem with the
software. Is there any reason why I shouldn't be able to include an
"execute process" task that calls a batch file that calls external programs?
Any ideas? Thanks.

Dave

No really unless the external exe requires user input. Also note that DTS is a user side application so if you execute the package
on your workstation even when you retrieve it from the "Local Packages" folder on a different server it will execute in the context
of your workstation.

Do you have everything you need installed on the server?
Do you have all the permissions required on the server?

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

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com


"Dave B" <daveb (AT) atgnet (DOT) com> wrote

I am have a similar issue. I am calling a batch file which calls an encoded
VBScript which encrypts a file and then FTP's it. The batch file and script
work fine alone. When I create the step to call the batch file in my DTS it
also works fine. I then manually execute the DTS package and still have no
problem. If I close Enterprise manager and then re-open and try to run again
it fails (apparently on the script). I then go back into the DTS package and
open the properties for the step that calls the batch file. If I browse to
the batch file again and re-select it (the exact same file) and save my
changes, it runs fine again. (until I close Enterprise Manager and open it
again) I have tried playing with permissions on the batch, script, and
folder giving the system process full access to all. Still nothing. May be
a similar problem to Dave's.
Any help would be GREATLY appreciated. Thanks.
Dan

"Allan Mitchell" wrote: