Hi, I have build a package with XML File as Configuration base. Now, after deploying the package it does not take the config value, instead it takes the config from dev. environment. Changing the values does not refresh package settings. I even restarted SQL agent service but to no use. Any ideas.Shady

Are you saying that even after changing value in the config file on your dev machine it does not refresh your package setting. If no, then it means that your deployed packages are still pointing to the xml file on the dev machine. During development try to specify a file path with a generic drive like I:, J: when using xml configurations. The way to do it would be, on your dev machine map one of the local folders as this generic drive and save all your xml configuration files in this local folder. When the package is deployed, make sure that on your deployment server either this generic drive is a physical drive or a again a mapped drive like above. This make your SSIS packages self-adjusting when moving between different environments.~V

Hi Shady, The Agent runs under an account that has no access to the directory where the config file is, e.g this happens when a developer places it on a share. You must recover by providing a UNC path (full path), and/or running the Agent job step involving SSIS packages using a proxy account with all the proper rights.Arthur My Blog

Hi, You may be right. I need to deploy package on SQL Server 2008R2 with WIN 2008. What user/security context is best ? Should I create a User and A) Assign it to Windows Admin group B) Assign it to SQL Admin Group C) Run Job under its identity. Shady

See this how to use a proxy: http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/Arthur My Blog