Koen Verbeeck (8/6/2013)
Quote from this MSDN page: Package Configurations.1. The dtexec utility loads the package.
2. The utility applies the configurations that were specified in the package at design time and in the order that is specified in the package. (The one exception to this is the Parent Package Variables configurations. The utility applies these configurations only once and later in the process.)
3. The utility then applies any options that you specified on the command line.
4. The utility then reloads the configurations that were specified in the package at design time and in the order specified in the package. (Again, the exception to this rule is the Parent Package Variables configurations). The utility uses any command-line options that were specified to reload the configurations. Therefore, different values might be reloaded from a different location.
5. The utility applies the Parent Package Variable configurations.
6. The utility runs the package.
Are you being bitten by number 4?
It would seem so, but #4 does state that it uses command-line options to reload the config file. So why is it not reloading those when it did before without problem?
I've verified that the config file is the same, that the job step command-line is exactly the same. The only changes I made were to fix the metadata of my Source and Destination in the Data Flow Task due to an additional column being added in the schema.
And I'm not using a Parent Package. This is a stand alone package that we keep in TFS.