April 13, 2015 at 9:21 am
I'm trying to get an FTP task to work. In this case I'm FTP'ing from an IBM mainframe. I tested the connection options from the command line and then configured the FTP task to match. When I run the package, it appears to get stuck at the FTP task. That is, it just sits there without proceeding or timing out.
To try to see what's going on, I enabled SSIS logging (all events) for the task. In the Log Events window I see only two entries for the task:
OnPreExecute
OnExecStatusChanged
After that, nothing. In fact, as I write this, the package is still, apparently, running and apparently executing the FTP task. However, as far as I can see, nothing is happening.
Questions:
1. What is going on here?
2. Why is the FTP task not doing anything and also not failing?
3. Is there an configurable timeout for this task (I couldn't find one)
Gerald Britton, Pluralsight courses
April 13, 2015 at 10:12 am
To be honest, I like to stay away from the built-in FTP task as I always seem to encounter issues with it.
My guess with the limited information is that it is stuck on the authentication step, and therefore no progress. In my opinion, it would be a better use of your time to write some .NET code in a script task to facilitate the FTP process.
April 13, 2015 at 11:53 am
Hi
Please take a look for link:http://winscp.net/eng/docs/guide_ssis#ssis_task. Imho
it is much a better solution than the built-in FTP Task.
Regards
Mike
April 13, 2015 at 2:14 pm
Martin Schoombee (4/13/2015)
To be honest, I like to stay away from the built-in FTP task as I always seem to encounter issues with it.My guess with the limited information is that it is stuck on the authentication step, and therefore no progress. In my opinion, it would be a better use of your time to write some .NET code in a script task to facilitate the FTP process.
Apparently it was actually a firewall issue. I ran it from a different machine and got past that, then hit a brick wall:
the FTP task "requires" that the remote path begin with a "/". A show stopper for me, since the FTP host (an IBM mainframe) has different filesystems and distinguishes them by the first character. Turns out that the path I want CANNOT begin with a "/".
So, I cobbled together a simple Script task to do it. Took all of ten minutes.
Gerald Britton, Pluralsight courses
April 13, 2015 at 2:20 pm
Yep, there are certain things I just don't do with the built-in tasks (and developing a .NET script is fairly easy for these):
August 12, 2015 at 7:55 am
would you by chance be able to post that simple .net code for ftping here? I could use that right now... Thanks
August 12, 2015 at 9:22 am
Kevin Bernard (8/12/2015)
would you by chance be able to post that simple .net code for ftping here? I could use that right now... Thanks
Unfortunately do not have something handy right now, but a simple google/bing search will bring back a ton of .NET samples specifically for FTP processes. Here's one result I found: https://msdn.microsoft.com/en-us/library/system.net.ftpwebrequest(v=vs.110).aspx
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply