SQLAgent job fails on FTP

  • Hi,

    I have an SSIS package which includes a series of FTP tasks taking files from a Unix server. Everything runs fine from VS2005, however now that I have created a job using the SQLAgent the job fails when trying to FTP.

    The other parts of the package run using the sqlagent, I can even send a mail from SSIS saying that the FTP task has failed and I am using the server account so I do not think it is an agent security issue.

    When I look at the connection string it only contains the IP address and port but no mention of the username and password for the Unix server (in the job step command line).

    In the package connection I have the username and password. The protection level on the package is set to EncryptSenstivewithUserKey but there doesn't seem to be an easy way to change it and changes do not seem to affect the agent command line.

    Does anybody know the syntax to add the username and password to the command line connection string ?

    Any advice welcome.

    Carl 

     

      

     

     

     

  • Bump. Anybody any ideas ?

  • i'm having the same problem.. please help!

  • Bump. Still no solution to this one ?

  • Bump.

    I got round this by firing some batch files but now I am starting version 2 of the project and seems a shame that MS has gone to the trouble of giving us an FTP task which is effectively unusable.

    Any ideas ?

     

  • If you're using package configurations, you'll need to make sure you check the 'server username' and 'server password' properties of the ftp task.. then you can go in and set the user/pass in the configuration file.

  • I am experiencing the same issue with using SQL Agent to run an SSIS package that has an FTP task component. I have had Microsoft on the phone for a couple of days now, but they do not have an answer yet.

    Could you describe how to display those properties in SSIS? I tried right clicking on the FTP task and also looking through the properties pane on my FTP task, but could not find them.

    Thanks,


    Cliff Norris
    Database Administrator
    Alston & Bird, LLP
    Atlanta, GA

  • I was having the same problem and it appears that I was able to resolve it by reimporting the package but setting the Package Protection Level to teh very last option in the dropdown list - Rely on Server Storage and Roles for Access Control.

    I hope this helps.

    Pat Byrne

    Programmer/Analyst

    Mobile County Public Schools

    pbyrne@mcpss.com

  • Update

    It is a while since I posted the original question. I have since had a few problems with the SQL Agent running SSIS packages.

    I seem to have overcome them all by setting up a credential and from that a proxy. I then use the proxy in the step that runs the package. The credential needs to be the same person as the one that last saved the package. At the moment all appears to be running fine.

    If anybody needs more details post back

    Carl

     

     

Viewing 9 posts - 1 through 8 (of 8 total)

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