I'm relatively new to SSIS and have not found my exact problem addressed in these forums. I have a package on my development machine that contains 8 connections, 15 data flows (each consisting of about 10 steps) and a series of SQL Execution tasks, Eventually I will need to bundle it up and ship it to another server (outside my network). I understand that the easiest way to do this is to deploy it to the file system and use a config file. I would have one here holding my credentials and the destination would have another with their credentials (correct?). So my package was running really well... a super improvement over the existing SQLServer 2000 DTS package currently in production. I enabled Package Configurations, and created an xml file that contained only the connection properties. Check the directory and the .dtsconfig file exists, Save and Build, the .dtsconfig file is gone. Because of that, I think, now if I close and reopen my project all of my connections have to be reconfigured and all of my dataflow tasks have to be opened and at least one of the sources or destinations has to be opened and columns viewed in order to get rid o the warning flags. Where is my .dtsconfig going and why? Additionally, I am now consistently getting the following error even when the .dtsconfig file is present: [Execute SQL Task] Error: Failed to acquire connection "connection_name". Connection may not be configured correctly or you may not have the right permissions on this connection. Prior to trying to set up configuration I was getting no errors and the package was running perfectly. What am I doing wrong or not understanding? I do not find either of these specific issues addressed in the documentation, but I admit I find the documentation very hard to follow.Jody

Is the main issue loss of the .dtsconfig file? Did you try looking for it? It simply just cannot disappear.Arthur My Blog

What location did you choose for your dtsConfig file? Was it somewhere under the Project folder? Like maybe in the \Bin folder? If so then I could see why it might get cleared out when you do a Build, which, by design, refreshes the contents of the folder as defined in the Project Properties.Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

Yes... I looked for it. It does simply disappear.Jody

Then please reply to Todd to confirm or deny that theory.Arthur My Blog

Thank you so much Todd! It was saved to the directory under the bin/deployment directory of the project. I created the config files in a higher level directory, then did a Build, and now they are being recreated in the bin\deployment directory instead of disappearing. Is that normal? If so, I'm confused about how to change credentials at my deployment location since they will get my credentials in the deployment package. Just edit the xml file? But there still remains the error problem on the Data Flow tasks: [Execute SQL Task] Error: Failed to acquire connection "connection_name". Connection may not be configured correctly or you may not have the right permissions on this connection. I get this error on SQL Execution Tasks: [CL tblName [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Connection_Name" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. All of my sources and destinations are viewable/previewable and all of my SQL tasks parse. Why am I getting a connection error that I wasn't before? Viewing the new config file shows UserName and Password. New information... Executing a task is now producing these addional warnings: Warning loading Project_name.dtsx: The configuration file "file_name.dtsConfig" cannot be found. Check the directory and file name. Warning loading Project_name.dtsx: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed I can edit the configuration file in it's upper level location and it also exists in the deployment directory. Don't know why dtsx can't find it. Jody