The idea is to make the connectionstring property of the oledb connection
dynamic (Which is in connection manager).

Using the wizard, created a package configuration file called
Configurations.dtsConfig

Opened it in notepad and placed the connectionstring inside
<ConfiguredValue></ConfiguredValue>

I would like to be able to only change this value in this file and all the
packages just refer to this.



Here is what is inside this created file.



<?xml
version="1.0"?><DTSConfiguration><DTSConfigurationHeading><DTSConfigurationFileInfo
GeneratedBy="EUGTUD099\GBPakd" GeneratedFromPackageName="BaseProfiles2"
GeneratedFromPackageID="{D441158B-8A31-4FE7-B051-3262737F74D6}"
GeneratedDate="07/08/2007 10:55:14"/></DTSConfigurationHeading><Configuration
ConfiguredType="Property"
Path="\Package.Connections[CounterpartyExposure].Properties[ConnectionString]"
ValueType="String"><ConfiguredValue>Data Source=servername1\instanccename1,
2025;Initial Catalog=databasename1;Provider=SQLNCLI.1;Integrated
Security=SSPI;Auto Translate=False;
</ConfiguredValue></Configuration></DTSConfiguration>



This is the error:



Error: 2007-08-07 10:58:26.07
Code: 0xC0202009
Source: BaseProfiles2 Connection manager "CounterpartyExposure"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has
occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for ODBC
Drivers" Hresult: 0x80004005 Description: "[Microsoft][ODBC Driver Manager]
Data source name not found and no default driver specified".
End Error

Can your package definitely "see" the configuration file? I use indirect
configurations to have the location held in an environment variable - might
be worth considering using this. Actually I'd recommend storing all the
configuration values in SQL server if at all possible.
HTH,

Hi,
I am trying not to use configuration package now.
The previous post shows what I am doing with the connectionPath variable.
But not sure why it gives the mentioned error?
Thanks

[quoted text, click to view]