ssissql-server-2016sql-jobkingswaysoft

SSIS Deployed Project validates Succesfully even with wrong Kingswaysoft Connection parameters

I deployed a SSIS project with a pre-configured Kingswaysoft connection, a project connection.

I created different environments inside the SSISDB database, and I want to validate the project with every one of them.

I intentionally set wrong connection parameters to see the validation fail, but instead the result was OK.

Everything was put correctly, env variables linked to conn manager properties, etc.

How is it possible? Is the project validating with the first pre-configured connection set in design mode?

Only when I try to run a SQL Job with the wrong environment params it crashes, but I want to be able to trust the previous validation process.

Solution

  • Proper way to set up this found here:

    http://www.kingswaysoft.com/blog/2019/11/14/Parameterizing-CDSCRM-Connection-Manager