June 16, 2015 at 5:41 pm
We've been upgrading our SSIS projects from 2012 to 2014, and I've run into a problem with the native FTP task. I have a package that compresses several csv files into a zip file and then uploads it to an offsite FTP server. The vendor at the receiving end is reporting that the zip files they're receiving are corrupted.
Using breakpoints to troubleshoot, I've confirmed that the file is intact before it is uploaded. The FTP task then runs to completion and reports success. However, when I download that file back off the FTP server and open it in WinRAR, I get an error that says, "Unexpected end of archive". WinRAR can still read the contents, but the last csv file is missing.
When I transfer the zip file manually to the FTP server, the file goes through intact. But when I transfer it via the SSIS task, it corrupts the file. The only conclusion I can figure is that the task itself is broken. Can anyone confirm?
I'm using SS v.12.0.2000 (Standard on the server and Developer locally).
Note that this same package works perfectly on SS v.11.0.3000.
June 17, 2015 at 9:09 am
Just a thought, but could it be possible that your FTP task starts transferring the file before the archive is complete? To eliminate/test whether this is indeed the case, include a delay or waiting task that gives the operating system a second or two to finish up with the archive.
On another note, I have found the native FTP task to be buggy and unreliable. I usually use a .NET script to perform FTP operations.
June 17, 2015 at 9:33 am
Thanks for the reply, Martin. I used a breakpoint before the transfer task started and confirmed that the archive had been completely created. Good thought, though.
The .NET script is going to be my next approach. I was just hoping the native task would actually be functional.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply