Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2012 Forums
 SSIS and Import/Export (2012)
 FTP Transfer fails via Job Activity Monitor

Author  Topic 

akhlaq768
Starting Member

12 Posts

Posted - 2014-10-15 : 03:22:06
I have a SSIS package set up that will transfer a file from a location on the network drive and transfer it over FTP to another location.

When I manually run the package, the file is transfer with no errors. But when the job is automated (via Job Activity Monitor) the transfer fails, any ideas?

I have set the ProtectionLevel of the package to "EncryptSensitiveWithUserKey" and also converted the package to a Development Model. The settings for the FTP is saved within the package.

What am I missing? below is the error message

Executed as user: UHB\InfoSQLAgent. Microsoft (R) SQL Server Execute Package Utility  Version 11.0.5058.0 for 32-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  08:43:02  Error: 2014-10-13 08:43:03.72     Code: 0xC001405F     Source: ResearchWebsite      Description: Failed to decrypt an encrypted XML node because the password was not specified or not correct. Package load will attempt to continue without the encrypted information.  End Error  Error: 2014-10-13 08:43:25.71     Code: 0xC001602A     Source: ResearchWebsite Connection manager "FTP Connection Manager"     Description: An error occurred in the requested FTP operation. Detailed error description: A connection with the server could not be established  End Error  Error: 2014-10-13 08:43:25.71     Code: 0xC002918F     Source: FTP Task FTP Task     Description: Unable to connect to FTP server using "FTP Connection Manager".  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  08:43:02  Finished: 08:43:25  Elapsed:  22.932 seconds.  The package execution failed.  The step failed.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2014-10-15 : 13:00:33
It's likely due to the SQL Server service account not having permissions. That's the most common reason why a package fails when run as a job but not when run by a person.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page
   

- Advertisement -