Here is a solution. It took putting the psftp.exe file in the same directory you are running the batch job for SSIS to see it. Good luck this work for me
Bruce wrote:
SSIS package hangs when running simple Execute Process task
03-Apr-09
I have a dtsx package with a very simple Execute Process task .exe that just
saves a file in a directory. The package runs fine from Visual Studio, the
app runs fine on the SQL Server. However, when I run this package from a job
in SQL Server the package starts and hangs forever. The SQL Agent user is
currently an administrative user for testing, so why is the package hanging
Bruce
Previous Posts In This Thread:
On Friday, April 03, 2009 9:54 PM
Bruce wrote:
SSIS package hangs when running simple Execute Process task
I have a dtsx package with a very simple Execute Process task .exe that just
saves a file in a directory. The package runs fine from Visual Studio, the
app runs fine on the SQL Server. However, when I run this package from a job
in SQL Server the package starts and hangs forever. The SQL Agent user is
currently an administrative user for testing, so why is the package hanging
Bruce
On Saturday, April 04, 2009 11:36 AM
Dan Guzman wrote:
Is the executable a launched via execute process a WinForm application or a
Is the executable a launched via execute process a WinForm application or a
console application. The former might not run when scheduled via a job
--
Hope this helps
Dan Guzma
SQL Server MV
http://weblogs.sqlteam.com/dang
"Bruce" <***@fss.co.orange.ca.us> wrote in message news:AD35E04B-24BD-4717-87E5-***@microsoft.com...
On Monday, April 06, 2009 11:37 AM
Bruce wrote:
It's a WinForm application. Is there a reason it will not run?
it is a WinForm application. Is there a reason it will not run? I have bee
doing this in DTS packages for years with no problem
Thanks, Bruce
On Monday, April 06, 2009 2:32 PM
Bruce wrote:
I tried as a console application as well and also does *not* work.
I tried as a console application as well and also does *not* work
Bruce
On Tuesday, April 07, 2009 8:14 AM
Russ Loski wrote:
Does the file get saved to a network or local directory?
Does the file get saved to a network or local directory? When you say "run
fine on the SQL Server" how are you launching the package
Russ
On Tuesday, April 07, 2009 8:18 PM
Dan Guzman wrote:
The issue with a Wnform app is that there is no desktop when the process is
The issue with a Wnform app is that there is no desktop when the process is
launched from a service. This will prevent GUI events from firing and can
cause different behavior than when run interactively
Perhaps the difference is security context. Can you run the package
interactively when logged in as the SQL Agent account
--
Hope this helps
Dan Guzma
SQL Server MV
http://weblogs.sqlteam.com/dang
"Bruce" <***@fss.co.orange.ca.us> wrote in message news:A7263D89-B930-43E4-888E-***@microsoft.com...
On Wednesday, April 08, 2009 11:17 AM
Bruce wrote:
Sorry I haven't posted my resolution sooner.
Sorry I haven't posted my resolution sooner. The problem was related to
using a UNC path in the executable property rather than a local drive letter
path. If the latter is used, the package worked fine, but of course that
forces the package to only be installed on a specific server
After doing some research, the solution is to add \\server to the Local
Intranet sites zone in IE (the file:// protocol is added automatically), and
then to make sure the "launching applications and unsafe files" option is
enabled in the custom settings for the Local Intranet zone in IE. This
really has nothing to do with SSIS, but everything to do with the zone
settings in IE. It would have been nice to find a resolution to this easier,
but it now works
Thanks to everyone who responded
Bruc
"Bruce" <***@fss.co.orange.ca.us> wrote in message news:AD35E04B-24BD-4717-87E5-***@microsoft.com...
Submitted via EggHeadCafe - Software Developer Portal of Choice
How to display a Gravatar Image with 100 Percent Client Script Code
http://www.eggheadcafe.com/tutorials/aspnet/3c8a04cd-471e-48b7-8dcc-b0877c10ecb4/how-to-display-a-gravatar.aspx