I've got a strange situation here and can't seem to get to the bottom of it. I have a pretty simple SSIS package that creates a CSV file, renames it, and then FTPs it to an FTP site.
I'm not using the builtin FTP task object in SSIS because it needs to be a Secure FTP connection and the built in SSIS FTP task doesn't support that. Therefore im using an external program called WinSCP.exe (http://winscp.net/eng/index.php), which I call with the Execute Process Task control flow Item.
NOW, when I run this package in my BI environment it runs with no issues, creates the file, renames, calls my WinSCP executable with a few parrameters, and off it goes. When I deploy this package to my SQL Server, and run it on the server manually, it runs fine as well, it takes all of 10-15 seconds.
However, when i schedule this package in the SQL Agent, the step where it FTPs the file using the WinSCP.exe program hangs for sometimes an hour or more, and then it finally comes back and the file seems to have transmitted without any issues. It consistently behaves this way, running it manually locally, or after its deployed to the server works fine, but when its a scheduled job in the scheduler, it hangs for an hour before it finishes the job. I'm pretty new at using SSIS so im not sure how to go about troubleshooting this type of behavior.
Anyone have any idea??
If you need any more details, please respond.
Dave