I've been copying a dtsx package that contains nearly all Execute T-Sql statement tasks. The engineer who built this sadly died in December, I'm just trying to do what needs to be done for my team's workload and pick up a lot of his work.

I'm no slouch with SSIS, but I've come across the weirdest thing that I can't understand. As I build each of the packages required for the overall solution and deploy them, they're fine up to now. This one and the next one I need to do, have 3 File Connection managers that are apparently redundant because they are used inside disabled tasks. I don't want to remove them because I don't yet fully understand if they are needed or not, and if they are, this issue will still be an issue.

To rule things out, I've re-enabled all but three of the disabled tasks thinking maybe they don't deploy because the tasks using them are disabled (the 3 tasks that remain disabled definitely need to be scrubbed at some point and don't use any of the mystery connections) and I've made sure that the .sql files that the connections are looking for exist in the same pathway on my machine and in the server (both have the same drive letter available fortunately).

No matter what I do, the 3 file connections just won't deploy with the package. I've tried deleting and recreating them. The connections are used in the three highlighted tasks:

These are the connections:

Each of them is variable controlled. The pathways in the variables are fine and the file exists at that location as previously mentioned.

The configuration in the package on the server should look like this (the top three are what's missing from the new one):

But it's always just like this:

Project level deployment doesn't work either, but none of these packages we have are built to deploy with project level connections anyway.

We have this same package deployed against every one of our clients. I've got another client's solution open that I'm copying from, checked every property and I can't see any differences that would stop these connection managers from deploying.

The issue is that until i can get them to exist in the configuration, even with the shown container and it's tasks disabled, the package fails because the connections aren't there. So it's looking for them even though they aren't being used.

We don't have any detailed documentation for this. It was something our engineer inherited and he's just made the best of it in his time.