FTP Task fails "unable to connect", FTP Connection Manager tests is SUCCESS

  • I have 2005 FTP task converted to 2008. The FTP task fails with

    [FTP Task] Error: Unable to connect to FTP server using "ServerFTP".

    When I test the connection in the connection manager, inserting the stored password manually, it works. Any ideas?

    I know there are comments about FTP tasks not being secure, but it appears this has worked in the past. Sorry for the drama, but getting an answer for this could help me keep my job.

    <><
    Livin' down on the cube farm. Left, left, then a right.

  • Have you tried deleting the connection in the connection manager and recreating it?

  • If it's a download task, it will fail if the file it's looking for isn't there. No way to simply re-route the process if the file isn't there, it just throws an error. Possible that's the issue?

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • I recreated the task, but not the connection manager.

    It is possible that the file does not exist. I will check.

    Thanks.

    <><
    Livin' down on the cube farm. Left, left, then a right.

  • I recreated the connection manager, but it still failed. It also looks like it created a password, even though I had not given it one. I created another with the passeword in hand but it failed also.

    I checked and the file exists.

    I would appreciate any further input you have.

    <><
    Livin' down on the cube farm. Left, left, then a right.

  • The FTP creates its own password, and I can not change it? Any ideas what might be wrong? It doesn't seem to me that that would be a preferred behavior.

    <><
    Livin' down on the cube farm. Left, left, then a right.

  • I have a package I need to work on today that will require an FTP task so I'll check it out. Unfortunately, I don't have a 2005 box handy so I won't be able to completely recreate all your conditions but I'll try to set it up in 2008 and let you know how it works out.

  • What's the ProtectionLevel property of the package set to? If it's "Don'tSaveSensitive" then the password cannot be stored by entering it into the connection manager, you must have a configuration file that populates the password property of the FTP Task and put the password in there.

    It's also possible that you have it set to "EncryptSensitiveWithAKey" and the upgrade process from 2005 to 2008 has broken the key management, so it's not able to decrypt the stored password at runtime. Does the output give a warning about failing to decrypt anything?

  • 2008 is my only concern. Thanks.

    <><
    Livin' down on the cube farm. Left, left, then a right.

  • HowardW (8/22/2012)


    What's the ProtectionLevel property of the package set to? If it's "Don'tSaveSensitive" then the password cannot be stored by entering it into the connection manager, you must have a configuration file that populates the password property of the FTP Task and put the password in there.

    It's also possible that you have it set to "EncryptSensitiveWithAKey" and the upgrade process from 2005 to 2008 has broken the key management, so it's not able to decrypt the stored password at runtime. Does the output give a warning about failing to decrypt anything?

    It is the former. The package is set to "Don'tSaveSensitive" so. And that makes perfect sense when you think about it.

    I have not found a "password property" for either the FTP task or the Connection Manager. The only way that I am aware to set a password is to re-write the connection string. Is that what you are thinking? (And my memory may be faulty). 🙂

    <><
    Livin' down on the cube farm. Left, left, then a right.

  • Sorry. Just reread your post Howard. You mention a config file not a property.

    BTW: Nice picture.

    <><
    Livin' down on the cube farm. Left, left, then a right.

  • Tobar (8/22/2012)


    HowardW (8/22/2012)


    What's the ProtectionLevel property of the package set to? If it's "Don'tSaveSensitive" then the password cannot be stored by entering it into the connection manager, you must have a configuration file that populates the password property of the FTP Task and put the password in there.

    It's also possible that you have it set to "EncryptSensitiveWithAKey" and the upgrade process from 2005 to 2008 has broken the key management, so it's not able to decrypt the stored password at runtime. Does the output give a warning about failing to decrypt anything?

    It is the former. The package is set to "Don'tSaveSensitive" so. And that makes perfect sense when you think about it.

    I have not found a "password property" for either the FTP task or the Connection Manager. The only way that I am aware to set a password is to re-write the connection string. Is that what you are thinking? (And my memory may be faulty). 🙂

    OK, that sounds like the problem. I'm about to leave the office, but this article should give you the main steps to create a config file:

    http://www.sqlservercentral.com/articles/Integration+Services+(SSIS)/66500/

    Basically, you only need to tick the password property (you can tick more if you want them to be configurable), which will be under the FTP Connection Manager in the Package Configuration Wizard. Once it's created the file, edit it and add the password in the appropriate place within the file (in the <ConfiguredValue> tag for the password property)

  • Thanks. That will be very helpful.

    <><
    Livin' down on the cube farm. Left, left, then a right.

  • Thanks. That did the trick!

    <><
    Livin' down on the cube farm. Left, left, then a right.

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply