SSIS Package Failing in SQL Agent – "Failed to load task" After SQL Server Upgrade

SSIS PowerPack
, ,
1

Question

After upgrading from SQL Server 2016 to SQL Server 2019 (or opening older SSIS packages in a newer Visual Studio environment), SSIS packages that use ZappySys tasks fail when executed via SQL Server Agent with an error like:

Error: Failed to load task "Encrypt_Access_Token", type "".
Error: The package cannot execute because it contains tasks that failed to load.
DTExec: The package execution returned DTSER_FAILURE (1).

Or in Visual Studio, ZappySys tasks appear with an error:

The task with the name "Encrypt_Access_Token" and the creation name "SSIS.ReplacementTask" 
is not registered for use on this computer.

Why does this happen, and how do you fix it?

Why Does This Happen?

When SSIS packages are created in an older Visual Studio / SQL Server version (e.g., VS 2016 / SQL 2016) and then opened or executed in a newer environment (e.g., VS 2019+ / SQL Server 2019), the SSIS runtime can no longer locate or load the ZappySys task registrations from the older package format.

The most common causes are:

  1. Package version mismatch — The package’s TargetServerVersion still targets an older SQL Server runtime (e.g., 2016), but SQL Server Agent is running the package using a newer DTExec runtime (e.g., SQL Server 2019, version 15.x).
  2. Corrupted or improperly imported packages — Packages moved or imported between environments can lose task mapping references during the process.
  3. SSIS PowerPack not registered on the server — The ZappySys components may not be installed (or correctly reinstalled) on the SQL Server machine where the Agent job runs.
  4. SQL Agent service account permissions — The service account running the job may not have access to ZappySys installation folders.

Solution

Work through the steps below in order. Most cases are resolved by Step 1 or Step 2.

Step 1 – Reinstall SSIS PowerPack on the Server

Even if the latest version is already installed, a clean reinstall is often the fastest fix for task registration issues.

  1. Uninstall SSIS PowerPack from the SQL Server machine.
  2. Restart the server.
  3. Download the latest installer from zappysys.com/products/ssis-powerpack/download/.
  4. Run the installer as Administrator, keeping the default installation options.
  5. Restart the SQL Server Integration Services (SSIS) Windows service.
  6. Re-run the SQL Agent job and check if the error is resolved.

Step 2 – Re-export Packages from the Original Environment

If the packages were copied or imported and are now corrupted, the cleanest fix is to go back to the source:

  1. Open the original/older UAT or source server where the packages were working.
  2. Export the packages directly from that environment (do not copy .dtsx files manually between environments).
  3. Import the freshly exported packages into your new Visual Studio project.
  4. Allow the package upgrade prompt when opening in the new VS version.
  5. Save and redeploy.

Step 3 – Update TargetServerVersion

If packages still have an older target version set, update it to match your current SQL Server:

  1. In Visual Studio, right-click the SSIS project → Properties.
  2. Under Configuration Properties, find TargetServerVersion.
  3. Set it to match your SQL Server runtime — e.g., SQL Server 2019 if your Agent is running DTExec 15.x.
  4. Save all, rebuild, and redeploy.

:warning: Important: The TargetServerVersion in the project must match the SQL Server version used by SQL Agent. A mismatch is one of the most common causes of “Failed to load task” errors.

Step 4 – Fix Package Format via Text Editor (Advanced)

If you have packages that cannot be re-exported and the above steps don’t resolve it, you can manually update the package format reference inside the .dtsx file:

Open the .dtsx file in a text editor (e.g., Notepad++) and find/replace the ZappySys assembly version string:

From (old format) To (target format)
ZappySys.PowerPack100 SQL 2008 → replacing
ZappySys.PowerPack110 SQL 2012 format
ZappySys.PowerPack120 SQL 2014 format
ZappySys.PowerPack130 SQL 2016 format
ZappySys.PowerPack140 SQL 2017 format
ZappySys.PowerPack150 SQL 2019 format ← most common target

For example, if upgrading from SQL 2016 to SQL 2019, do a bulk find & replace of ZappySys.PowerPack130 → ZappySys.PowerPack150 across all .dtsx files in your solution folder.

:light_bulb: Make a backup of all files before editing.

Step 5 – Verify SQL Agent Service Account Permissions

The SQL Agent job in the ticket ran as QAS\SQLClustSVC. Ensure this account has:

  • Read/execute access to the ZappySys installation directory (typically C:\Program Files\ZappySys\)
  • Access to the SSISDB or the package file location
  • Access to any referenced connection files or configurations

Quick Checklist

Check Details
:white_check_mark: SSIS PowerPack installed on server? Must be on the SQL Server machine, not just the dev machine
:white_check_mark: 64-bit version installed? SQL Agent typically runs 64-bit DTExec
:white_check_mark: TargetServerVersion matches SQL Server? Project properties → must match Agent’s runtime version
:white_check_mark: Package re-exported (not just copied)? Copied packages can be corrupted
:white_check_mark: Service account has permissions? Check access to ZappySys folders

Contact Us

If you encounter any further issues or need additional help, please reach out to our support team via live chat or submit a support ticket at support@zappysys.com.