SFTP Task Failure Error when exucting package from SQL Agent Jobs

Aug 2, 2016 at 4:07 PM
I have an SSIS package using the SFTP Task that runs fine in Visual Studio 2015 but when I try to schedule the package to run in SQL Server 2014 Jobs it gets the error below.
DLL installed is C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Tasks\SSISSFTPTask120.dll

Error from Log:

Date 8/2/2016 11:59:32 AM
Log Job History (Merkle Reports)

Step ID 1
Server DEN114LR90JRA8A
Job Name Merkle Reports
Step Name Merkle Reports
Duration 00:00:01
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 12.0.4100.1 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:59:32 AM Error: 2016-08-02 11:59:33.17 Code: 0xC001F02A Source: Package Description: Cannot create a task from XML for task "SFTP Task", type "SSISSFTPTask120.SSIS.SSISSFTTask, SSISSFTPTask120, Version=, Culture=neutral, PublicKeyToken=ad434584aa4b647a" due to error 0x80070057 "The parameter is incorrect.". End Error Error: 2016-08-02 11:59:33.17 Code: 0xC0010018 Source: SFTP Task Description: Failed to load task "SFTP Task", type "". The contact information for this task is "cosmin.vlasiu@gmail.com". End Error Error: 2016-08-02 11:59:33.25 Code: 0xC0010026 Source: SFTP Task Description: The task has failed to load. The contact information for this task is "cosmin.vlasiu@gmail.com". End Error Error: 2016-08-02 11:59:33.25 Code: 0xC0024107 Source: SFTP Task Description: There were errors during task validation. End Error Error: 2016-08-02 11:59:33.25 Code: 0xC0010025 Source: Package Description: The package cannot execute because it contains tasks that failed to load. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:59:32 AM Finished: 11:59:33 AM Elapsed: 0.421 seconds. The package execution failed. The step failed.
Aug 5, 2016 at 5:45 PM
Did you install the SFTP task on the server running the job or did you only install it locally?
Aug 9, 2016 at 11:51 PM
I figured it out. It's because the server was trying to run the package in 64 but not 32. Sent from my iPhone