FTP task fails on timeout, Exception from HRESULT: 0xC001602A

Question

I wanted to "thank" the SSIS team for their traditionally wonderful job at error handling. From what I understand the 0xC001602A is a catch-all for pretty much any and every problem, which I personally find incredibly helpful when debugging a "weird" problem. But enough with the well-deserved praise, let's turn to the problem at hand.

I have an FTP task that basically goes places and get me all XML files from that directory. It is a standard "Receive files" not a script, and when I try it on VS 2005 with SQL 2005 on x86 XP Machine it works like a charm. From the same network to the same FTP server running from VS 2008 with SQL 2008 on x64 Win 2008 machine it gives me the timeout exception. 32 bit filezilla runs fine on both platforms, so the issue is not the network, nor permissions. The issue is that I created a blank package, and than added a singular task, setup an FTP Connection in the Manager, and tested it successfully. When attempted to run it produced an error message saying that task timed out, which is funny since the task was set to time-out in 60 seconds, but came back in 30. I'm not a great specialist, but I am running against a deadline so any help, that is actually helpful is appreciated.

Thanks
Vadim

Actual Output: "0xC001602A at Package2, Connection manager "FTP Connection Manager": An error occurred in the requested FTP operation. Detailed error description: The operation timed out"

Answer 1

No solution so far. I had implemented a work-around, but installing a share on the Red Hat, and then in the ForEach loop implementing a file read, a file copy and a file delete as sequential operations. For some reason File Move did not work, most likely due to permissions issues on the Linux side. The combination of copy file, and delete file, while may not be ideal, is clearly workable.
BTW I do believe this is an MS-bug, since the same FTP worked fine from an XP machine.

Answer 2

I am experiencing the exact issue running Windows7 x64. I created an SSIS package in VS2008 which includes an FTP task. The package runs flawlessly on a WinXP 32bit on my network. In fact it works perfectly fine on a colleague's network on a Windows 2003 Server x86. So the package and the permissions and passwords are all properly configured.

I have tried every work around available for the last 3 days and nothing works. So the only conclusion I can draw by process of elimination is the x64 based OS.

Any feedback from the Microsoft contingent?

Answer 3

I also ran into this using Vista 64, then I wrote a FTP Script Task in C#, same issue, then I used plain old command line FTP and I can connect but as soon as I do a "ls" or "get" it would timeout. Of course everything works fine in a 3rd party client. So I spoke with our network people and the fix was simple: use passive mode in the FTP connection.

Answer 4

Good call! It fixed the problem on Windows7 as well.

Answer 5

has anyone submitted a bug report regarding this issue to connect ? if not, i think i would be helpful to others if it were.

---

Duane Douglas, MCAD, MCITP | http://www.ssisbi.com | Please mark the post(s) that answered your question.

Answer 6

I'm having the same exact problem, but the source site I need to retrieve files from demands and active connection, and disconnects anyone immediately who tries to retrieve files in passive mode. So, while the process works in XP (32bit), we need to have this running in a 64bit server environment... Have anyone found a proper fix for this issue yet or is passive mode all you needed?

Many thanks,
Philip de Souza

Answer 7

For everybody who has similar problem - as a workaround, package can be scheduled as a 32-bit job. 

Regards, Vlad.

Answer 8

Thank you! Setting the ftp connection to passive mode worked like a charm!

---

Francisco Isla, Technical BI Consultant

Answer 9

I also ran into this using Vista 64, then I wrote a FTP Script Task in C#, same issue, then I used plain old command line FTP and I can connect but as soon as I do a "ls" or "get" it would timeout. Of course everything works fine in a 3rd party client. So I spoke with our network people and the fix was simple: use passive mode in the FTP connection.

Just wanted to thank you for this.  Worked for me!