Griffster (7/20/2012)
OMG! That's worked! Is it best practice then to remove the configuration file when you're happy with the package? Really strange that. We've recently upgraded to SQL 2008 from 2005 and I never remember having this issue in SQL 2005 SSIS/SQL Agent...
The behaviour of SSIS package configurations has changed between 2005 and 2008.
Behavior Changes to Integration Services Features in SQL Server 2008
It's not really a best practice to remove your package configurations. What usually is done is that you have another package configuration that points to the location of the XML config file (usually an environment variable). This is called an indirect package configuration. If the package changes environment, it will pick up the new location of the config file.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP