Re: Shared Configuration file build problem

Ping

"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

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,

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
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:

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
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,



.

Relevant Pages

  • Re: Shared Configuration file build problem
    ... "Allan Mitchell" wrote: ... I select enable package configuration for Package1. ... I have placed the config file in the same directory as the ... I have tried with the AllowConfigurationChanges property set to ...
    (microsoft.public.sqlserver.dts)
  • Re: Shared Configuration file build problem
    ... "Allan Mitchell" wrote: ... I select enable package configuration for Package1. ... I have placed the config file in the same directory as the packages, ... I have tried with the AllowConfigurationChanges property set to true ...
    (microsoft.public.sqlserver.dts)
  • RE: Shared Configuration file build problem
    ... Ahhh more than one package. ... I can build succesfully when only 1 package has an xml config, ... I have placed the config file in the same directory as the packages, ... I have tried with the AllowConfigurationChanges property set to true ...
    (microsoft.public.sqlserver.dts)
  • Re: Import multiple mdb files to SQL Server issue: Please Help...
    ... "Allan Mitchell" wrote: ... Doing the loop inside the loop is fine but will involve a lot of coding if ... DTSStep_DTSActiveScriptTask_3 to take the next mdb file then do the ... DTSStep_DTSActiveScriptTask_3 is not the same in your package. ...
    (microsoft.public.sqlserver.dts)
  • Re: remotely call a DTS
    ... Allan Mitchell wrote: ... Denied on something inside the package. ... This worked when I was logged into the server and ran it from my ... but the DTS blows up. ...
    (microsoft.public.sqlserver.dts)
Loading