I have an SSIS Package, running in Package mode, in SQL 2012. This package sends a previously constructed .gz file to a client's FTP location. This package has been running flawlessly for months, if not years.
About two weeks ago, strange behavior emerged. The FTP Task runs and indicates success (in that the FTP Task returns a success condition). No configuration changes have been made. However, the file itself no longer shows up on the client's FTP site.
I went directly into the package code and, using the data in the FTP Connection Manager, was able to successfully transfer this file using an FTP Client (Filezilla). This gives me some assurance that the problem is at our end, and not at the client's. And, FWIW, I carefully tested to assure that the client's site wasn't executing some sort of sweep that might have removed the file. No, it really appears that the file never get's placed on the client's site.
But I get no error. The FTP task indicates success. And, unless there is a way I can tap into the FTP Communications exchange between the FTP task and the client site, there is no way I am aware of to be able to see exactly WHAT the FTP task thinks it is doing.
Occam's Razor would suggest the most likely scenario is that the data is successfully goingsomewhere else - but without access to the FTP stream, I cannot see what the task is ACTUALLY doing. Is there a way (short of putting a sniffer on the TCP/IP stream) to uncover the communications generated by the FTP Task?
I could, of course, completely re-write the FTP Task as a script and capture communications that way. But I have yet to see anything that would indicate this sort of false-success in a FTP task, and am seeking any insight or suggestions about ways to debug this issue.
To reiterate - this change in behavior occurred without a corresponding change in the package itself. It, apparently, just started happening. Right.
Any suggestions gratefully accepted.
Duncan Davenport
Bryant Chrisitie, Inc. Seattle, WA