• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 168
  • Last Modified:

SSIS FTP Task results

Is these a way to get the stdout from an ftp task?  

I was working on a large file issue, and when I ran FTP at dos prompt I discovered that it was out of disk space.  If I could see the error in SSIS, it would save lots of time.
0
No1Coder
Asked:
No1Coder
  • 5
  • 5
2 Solutions
 
AlexPaceCommented:
Do you mean the protocol-level log of the FTP session?
0
 
No1CoderAuthor Commented:
No.  I want to see the output as if I was running it from a command prompt.  Any error message, etc.  I want to put that information is a variable.
0
 
AlexPaceCommented:
The command prompt ftp.exe is a standalone FTP client program.  The SSIS task does not use that client for its connection.  It should, however, be able to create a log that will look something like what you might see if you ran ftp.exe in verbose mode.
0
2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

 
No1CoderAuthor Commented:
How do you create the log?
0
 
AlexPaceCommented:
I apologize I was mis-remembering a protocol-level trace log file I got by using an EXEC task to launch Robo-FTP and run a script.  That log was generated by Robo-FTP rather than by SSIS.  So I don't really know what SSIS is capable of as far as logging but I am sure it doesn't use ftp.exe because an FTP task can do Passive Mode but ftp.exe only does active mode.

So I would try setting the logging on the package itself to "verbose" mode and see if that provides enough information.  If that doesn't give you enough then you could use WireShark or other similar sniffer to log the text over the wire.  If you are more of an ftp.exe kinda guy than a WireShark kinda guy you could use an EXEC task to launch ftp.exe (1) in verbose mode and (2) pass the name of a script to run and (3) redirect output to a text file.  That should work as long as you can use Active mode.  If you need anything more than the most basic behavior then ftp.exe might not be appropriate for your needs.  WinSCP is free and has scripting that is a little better than ftp.exe and it has logging.  Robo-FTP is commercial but it has the best FTP scripting and support so it might be a good option if this is a project for work rather than for a hobby ore a favor.
0
 
No1CoderAuthor Commented:
I want to use the FTP task.  That is what it is for.  Is this just another limitation of Microsoft software, or is there a way to accomplish this?
0
 
dbaSQLCommented:
0
 
AlexPaceCommented:
@dbaSQL - cool, I didn't know you could do that!
0
 
No1CoderAuthor Commented:
Thanks for this, however this is not exactly what I was looking for.  I really wanted the "console output" (what you would see if you connected to the same site using command line FTP command).  I was under impression that SSIS just put a wrapper around the FTP command.  Just trying to get stdout.
0
 
AlexPaceCommented:
There is not an FTP command.
There is a tiny FTP client program named ftp.exe that you can use from DOS.
You can be 100% sure that SSIS does not use that program under-the-hood because it supports passive mode data channels and ftp.exe does not.
If I had to guess I would say their either wrote their own FTP client or they made a wrapper for the same functions that Internet Explorer uses.
That said, you really can use an execute process to launch ftp.exe and use it instead of the built-in FTP task...  and you really can redirect stdout from ftp.exe into a little text file that becomes your "log" of the FTP session, especially if you launch it in verbose mode.

Perhaps we don't need a log.  What is the actual problem that you are trying to solve?  If, for example, you have something that works in FileZilla but not in the FTP task the problem usually comes down to file and folder permissions...
0
 
No1CoderAuthor Commented:
The problem is the ftp task was failing, and there was no indication of why.  I discovered (using WSFTP) that the target server didn't have enough disk space.  This took a long time to figure out because there is no output from the FTP task.  All I want is for the task to provide some information as to why it is failing.  The FTP command log would probably work, but seems overkill.  If it isn't available, okay.  I am over the immediate hurdle anyway.  I really have wasted more time on this than I should have.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now