I have developed packages and have tested them on a test server in conjunction with using XML configuration files. Everything has worked fine in development. When I go to deploy to the production server I change the values in the configuration file to be that of the production server and everything seems to work just fine. However, when I run the package it doesn't execute on the production server but rather for some reason still executes on the development server. When installing the package I did notice that the Path has the development sever name in the path but I don't see a way to change it. I'm sure I'm missing something simple but I am struggling with why this isn't working. Thanks.

SSIS is a client application, therefore,the package runs on the machine you execute it from not on the machine it is located on. So if you execute it from the production server it will run on the prioduction server. If you execute it on the test server that is where it will run. If you execute it on you home pc it will run there. Obviously, SSIS would need to be installedin order to run it on a PC in any of those scenarios. Did I answer or did I misunderstand your question? Matt

1. May be your package internally has some reference to Development Server path, please review the package code & see if anything is hardcoded 2. In your config file, you may want to see if anything is suspicious 3. Ensure all the files are in appropriate folders 4. Can you step thru the package & put debug code

Hi,you should use envirronement variable to put the path of your configuration file.I think today the path of your configuration is hardcoded and there is no way to change it when deploying, except to edit manually the dtsx.Hope it helps.

I have the configuration in the same location on both the development and production servers. So the package should be finding the correct path to the configuration. I am able to change values when deploying the packages through the Package Installation Wizard. It installs without any issues or throwing any validation errors. However, when I run the package it errors out with the following error: Code Snippet Executed as user: EPNT\SQL2005. ...rsion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 12:15:50 PM Error: 2008-10-27 12:15:51.07 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2008-10-27 12:15:52.17 Code: 0xC0202009 Source: Scorecard Ssis DimensionLoad dimEmployeeLoad Connection manager "EVEREST.Scorecard.pacman" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'pacman'.". End Error Error: 2008-10-27 12:15:52.17 Code: 0x... The package execution fa... The step failed. It is interesting here that the Connection Manager indicates EVEREST. That's the Dev server, even though when I installed I changed it the production one (ISDEV). If I just open the configuration file directly and change every instance of EVEREST to ISDEV then it won't even install. I get error messages. Here is what one of the configuration files look like. Code Snippet <?xml version="1.0"?><DTSConfiguration><DTSConfigurationHeading><DTSConfigurationFileInfo GeneratedBy="EPNT\Ehlinger" GeneratedFromPackageName="Scorecard Ssis DimensionLoad dimEmployeeLoad" GeneratedFromPackageID="{020D85FB-E2FC-4FDA-B596-C0E2E699B7D4}" GeneratedDate="10/27/2008 12:00:37 PM"/></DTSConfigurationHeading><Configuration ConfiguredType="Property" Path="\Package.Connections[EVEREST.dw_scorecards].Properties[ConnectionString]" ValueType="String"><ConfiguredValue>Data Source=EVEREST;User ID=pacman;Password=XXXX;Initial Catalog=dw_scorecards;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[EVEREST.dw_scorecards].Properties[ServerName]" ValueType="String"><ConfiguredValue>EVEREST</ConfiguredValue></Configuration></DTSConfiguration> What am I missing here?

Further update. I am back to where I can install the package fine by changing the values in the config file through the installation. The package runs fine but still executes as though it is on the dev server. If I manually go in and change the values in the config file in its installed location then it throws errors indicating that the metadata needs to be updated.

The first error can be fixed by ticking the box that says something like "use sql server location for encryption" when deploying the SSIS package. Also, make sure that your connections (data sources) are actually pointing to the correct server. I'm doing exactly the same thing, and one of my flat files was never changing, even though I was altering the config files. In the end, I found it was one particular connection to a flat file that was the problem.

I am not finding the box about "use sql server location for encryption" when deploying the SSIS package. The connections are pointing to the correct server in development. The configurations are in the same location on both the dev and production servers.In the configuration file I am specifying the ConnectionString and ServerName.On the production server I am opening the config file in notepad and changing the Data Source in the ConnectionString to the production server and the ServerName attributes.(As a side note, when installing the packages it appears that the wizard allows you to change these attributes in the configurations but that doesn't seem to work.)After having changed these attributes in the configuration files, the package fails when running it as a job.It is indicating that it needs new Metadata.The same thing happens if I change the configuration files and then try to re-install them.I get validation warnings in the installation indicating the same thing.Here is the actual error from the history log:Executed as user: EPNT\SQL2005. Microsoft (R) SQL Server Execute Package UtilityVersion 9.00.3042.00 for 32-bitCopyright (C) Microsoft Corp 1984-2005. All rights reserved.Started:10:07:16 AMError: 2008-10-28 10:07:17.37 Code: 0xC004706B Source: DTF Loading Employee Dimension DTS.Pipeline Description: "component "OLE_SRC_Employee" (1)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".End ErrorError: 2008-10-28 10:07:17.37 Code: 0xC004700C Source: DTF Loading Employee Dimension DTS.Pipeline Description: One or more component failed validation.End ErrorError: 2008-10-28 10:07:17.37 Code: 0xC0024107 Source: DTF Loading Employee DimensionDescription: There were errors during task validation.End ErrorDTExec: The package execution returned DTSER_FAILURE (1).Started:10:07:16 AMFinished: 10:07:17 AMElapsed:0.828 seconds.The package execution failed.The step failed.Conceptually, configuration files sound great and are a usefull tool.Unfortunately, I am missing something and it is probably a pretty easy item but I just can't seem to find it.Thanks for your help and hopefully you'll be able to indicate what I'm missing.

There is now an open source utility available in CodePlex which can be used to batch update SSIS Package Configuration File paths without using BIDS or manually editing the package XML: http://ssisconfigeditor.codeplex.com/