I have a project with 12+ packages, all using a shared config file.
I have placed the config file in the same directory as the packages, and all
of the packages are using relative file paths to find it.

When I set my Project Settings to CreateDeploymentUtility=true, I get a
build error saying that the config file cannot be copied because it already
exists.
I have tried with the AllowConfigurationChanges property set to true and
false, but this doesn't help.

Thanks in advance for any help on this,

I have tried again on a smaller scale project (2 packages).
I can build succesfully when only 1 package has an xml config, but as soon
as I point the second package at it I get the build error.

Have I got the wrong end of the stick here?
I keep seeing references to shared config files, and I really only want to
have 1 config file to maintain.

Getting a bit desperate now...

"programmer_mike" wrote:

Hello programmer_mike,

I saw this error this week in class. I deleted the file form the location
dpeocified in the configurations. That said I am trying to repro your issue.
I have created a config with a path to the XML file of

\NameOfFile.dtsConfig

This works fine for me.

Can you tell me more about the setup and your error?


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Hello programmer_mike,

Ahhh more than one package. Looking at it now

Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

I now have a simple test system set up for this.

I have 2 packages (just issuing sql select staments).

Project builds ok

I select enable package configuration for Package1.
I go through the wizard, selecting xml, and selecting the connection string
properties to be saved.

I've tried linking to a fully qualified path, just giving the file name, and
putting a "\" in front of the file name as you indicated.

All is well until I cinfigure the second package.
I specify the file, it prompts me to "Use Existing File" (which I agree to)
and I follow the wizard through a second time.

Then I get the build error.
I'm using Microsoft SQL Server Integration Services Designer
Version 9.00.1399.00

Let me know if you need any more info, and thanks for taking a look at this.

Mike

"Allan Mitchell" wrote:

I fully appreciate that everyone has very busy workloads, but I have now
spent ages on this and its holding up the deployment of my project.

I have tried everything I can think of and the whole area of config files is
giving me endless problems.

If someone could help with this problem I would be eternally grateful.

"programmer_mike" wrote:

Hello programmer_mike,

I can repro quite happily i just cannot get the fix I used last week to work.
My experiment says you can delete the config files and still builld the
solution.



Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Allan,

Thank you for your help so far.
I am now using master package variable to get me working, but I would much
prefer to use configuration files.

Can you advise me on how I can progress this issue. Does it need to be
reported as a bug?

Thanks again,

Mike
"Allan Mitchell" wrote:

Hello programmer_mike,

Let me have a play and an ask around. Can you ping me in a couple of days
and we can take it from there unless anybody else has experience of this.

Whilst I do not want to call it a bug right now I am having a hard time getting
it to work properly



Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Ping

"Allan Mitchell" wrote: