I have a SSIS SQL server 2014 package that doesn't load the connection manager connection string from the configuration file.
I have a Dev server that I can run the package using SSIS 2014. If I change the configuration file to an invalid server and then run the sql agent job I get the expect error.
I then deploy the same package from SSDT to the "Prod server". The configuration is stored in the same folder path as Dev (D:\Config\...) but when I run sql agent I get an error stating it can't load the child packages from sql server location.
So I export the package from MSDB into the local file system (on Prod server), open the package using SSDT on the local server. The connection managers can read the config file (D:\Config\..) so I see the correct connection strings. I deploy from SSDT into MSDB (package deployment method). I can now run the sql agent jobs. Nothing has changed on the package, I even have the smae version numbr as the one in Dev. But I can run it now.
If I change the connection string on the configuration file to an invalid server name then run sql agent expecting to error it doesn't still runs succesfully. So that tells me the configuration is not being loaded.
What could be stopping the configuration file from being loaded?
When I deploy the package from SSDT on my local laptop to the prod server, the connection managers are using the setting set at design time and not the configuration file?
THis is very strange.