Greetings, have an issue applying xml config file in an agent job. We recently moved all of our code source from an old file server to a new file server so all of the config files now have a new path. They have new path because I used notepad to update all the packages (.dtsx files) with Notepad++ to replace the old file server to the new file server. This was done so when people open up a package on this server they have the valid configuration files.
We run the packages by copying the dtsx file to a SSIS/SQL server (not the same server where the source is located) and the corresponding config file(s) also to the server and update the config files as needed to change properties of values such as a connection string or email address. This had all been working fine until we move all the source to a new file server. The first time I made a change to a package and moved it to our production SSIS/SQL server and ran the existing agent job it failed. Not a lot of helpful messages in the log but I do have some error handling and one of the messages I get shows me that it is trying to connect to the original dev server settings so it is not applying the xml config file to override these connection strings. What I have come up with is permissions are probably differnt on the old source server and new source server for the account running SQL Agent and thus running these packages. I believe it was in the local admins on th old file server and not on the new file server so as it tries to apply the configuraitons from the orignal package it cant access the files and fails.
I am wondering how people handle this situation or if maybe someone has a differnt idea on what is going on?