SQL Server Agent Fails to Recognize ZappySys Connection Managers After Deploying to SSISDB

Tutorials SSIS Tutorials
1

Symptoms

After deploying an SSIS package containing ZappySys Connection Managers to SSISDB, you may notice one or more of the following issues:

  • Package executes successfully in Visual Studio but fails when run through SQL Server Agent.
  • ZappySys Connection Managers do not appear under the Configure tab in SSISDB.
  • Package execution fails with errors indicating that the ZappySys connection manager cannot be found or initialized.
  • The issue only affects packages containing ZappySys components, while standard SSIS packages run successfully.

Cause

This issue may be related to the deployment tool version used to publish the SSIS package to SSISDB.

In one reported case, packages were deployed using SQL Server Management Studio (SSMS) 17. Although the deployment completed successfully, the deployed package did not correctly register the ZappySys Connection Managers within SSISDB.

After redeploying the same package using SSMS 18, the connection managers became available in SSISDB and the package executed successfully from SQL Server Agent.

Resolution

If you encounter this behavior, try the following:

Option 1 - Verify the Deployment Tool

Ensure you are using a supported version of the deployment tool.

For SQL Server 2019, consider deploying the package using SSMS 18 instead of older versions of SSMS.

Option 2 - Redeploy the Package

After upgrading the deployment tool:

  1. Open the SSIS project.
  2. Redeploy the package to SSISDB.
  3. Verify that the ZappySys Connection Managers appear under the Configure section.
  4. Execute the package again using SQL Server Agent.

Additional Notes

  • This issue appears to be related to the deployment process rather than the ZappySys components themselves.
  • The deployment may complete without reporting any errors, even though the connection managers are not correctly registered in SSISDB.
  • If Visual Studio deployment is unavailable or freezes, verify that the alternative deployment tool version is compatible with your SQL Server version.

Environment

  • SQL Server 2019
  • SSISDB
  • SQL Server Agent
  • ZappySys SSIS PowerPack
  • SQL Server Management Studio (SSMS)

Conclusion

If ZappySys Connection Managers are missing after deployment to SSISDB or packages fail only when executed through SQL Server Agent, verify the version of the deployment tool used. Redeploying the package using a newer, supported version of SSMS (such as SSMS 18 for SQL Server 2019) may resolve the issue.

Note: This article is based on a customer-reported scenario. While the exact underlying cause has not been fully identified, the deployment method resolved the issue in that environment. If the problem persists, please contact ZappySys Support with your package details, deployment method, SQL Server version, and SSMS version.