Hi, I am probably missing something obvious here; - I have created a package with a variable named; - ServerName and a value of 'KIERAN-PC' I exported this variable as an SSIS configuration within a SQL Server table I noticed the following record appeared within the SQL Server configuration table. ConfigurationFilter ConfiguredValue PackagePath ConfiguredValueType tblSSISConfigurationFilter KIERAN-PC \Package.Variables[User::ServerName].Properties[Value] String I then changed the ConfiguredValue within the SQL Server configuration table record as follows; - ConfigurationFilter ConfiguredValue PackagePath ConfiguredValueType tblSSISConfigurationFilter localhost \Package.Variables[User::ServerName].Properties[Value] String I shut down my DTSX package and reopened it expecting the variable named ServerName to contain the value 'localhost' (to enable me to have many SSIS packages with the same configuration). The ServerName was still set to 'KIERAN-PC' Can anyone help? Kind Regards, Kieran. If you have found any of my posts helpful then please vote them as helpful. Kieran Wood MCTS BI, PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds

Thanks Todd, I've set a watch on the variable ServerName. After the first task in the Control Pane was successfully executed the cursor is paused on the task task. The value of the variable is still 'KIERAN-PC' where the value of the related row in the SQL Server configuration table is 'localhost'. I may be missing something here, but I still don't know what! Thanks again, Kieran.If you have found any of my posts helpful then please vote them as helpful. Kieran Wood MCTS BI, PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds

Can you try an XML configuration file? Perhaps there's something messy in the connection to your server. Do you see "information" messages in your Output window when you start the package, similar to this: Information: 0x40016041 at <package name>: The package is attempting to configure from ... Talk to me now on

OK, will do Todd. Thank you for persisting with me, this issue is driving me potty!If you have found any of my posts helpful then please vote them as helpful. Kieran Wood MCTS BI, PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds

Configurations (like many things in SSIS) can be tricky to get working the first time. The crazy part is that once you do it, you can't seem to remember why it was hard the first time. Talk to me now on

Is anything getting set via expressions?...maybe something hardcoded?

Thanks Todd, I've created several SSIS configurations before. Following your advice again my Output Window looks very weird, so I will re-create my package step by step. This is a bit of de-ja-vue I seem to be getting lots of corrupt packages. I wonder what the most common cause of this problem is? Information: 0x40016040 at ErrorTemplate2: The package is attempting to configure from SQL Server using the configuration string ""Server.ErrorLog";"[dbo].[tblSSISConfigurations]";"tblSSISConfigurationFilter";". Warning: 0x80012018 at ErrorTemplate2: The configuration entry, "", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" to the package path. Warning: 0x80012017 at ErrorTemplate2: The package path referenced an object that cannot be found: "". This occurs when an attempt is made to resolve a package path to an object that cannot be found. Warning: 0x80012018 at ErrorTemplate2: The configuration entry, "]", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" to the package path. Warning: 0x80012017 at ErrorTemplate2: The package path referenced an object that cannot be found: "]". This occurs when an attempt is made to resolve a package path to an object that cannot be found. Warning: 0x80012018 at ErrorTemplate2: The configuration entry, "", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" to the package path. Warning: 0x80012017 at ErrorTemplate2: The package path referenced an object that cannot be found: "". This occurs when an attempt is made to resolve a package path to an object that cannot be found. Warning: 0x80012018 at ErrorTemplate2: The configuration entry, "", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" to the package path. Warning: 0x80012017 at ErrorTemplate2: The package path referenced an object that cannot be found: "". This occurs when an attempt is made to resolve a package path to an object that cannot be found. Warning: 0x80012018 at ErrorTemplate2: The configuration entry, "]", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" to the package path. Warning: 0x80012017 at ErrorTemplate2: The package path referenced an object that cannot be found: "]". This occurs when an attempt is made to resolve a package path to an object that cannot be found. Warning: 0x80012018 at ErrorTemplate2: The configuration entry, "]", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" to the package path. Warning: 0x80012017 at ErrorTemplate2: The package path referenced an object that cannot be found: "]". This occurs when an attempt is made to resolve a package path to an object that cannot be found. Warning: 0x80012018 at ErrorTemplate2: The configuration entry, "]", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" to the package path. Warning: 0x80012017 at ErrorTemplate2: The package path referenced an object that cannot be found: "]". This occurs when an attempt is made to resolve a package path to an object that cannot be found. Warning: 0x80012018 at ErrorTemplate2: The configuration entry, "", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" to the package path. Warning: 0x80012017 at ErrorTemplate2: The package path referenced an object that cannot be found: "". This occurs when an attempt is made to resolve a package path to an object that cannot be found. SSIS package "ErrorTemplate2.dtsx" starting. SSIS breakpoint 'Break when the container receives the OnPreExecute event' at executable 'Execute SQL Task Deliberate Error' has been hitIf you have found any of my posts helpful then please vote them as helpful. Kieran Wood MCTS BI, PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds

Many thanks again to everyone who has helped me with this issue. I have re-created a SSIS configuration based on an SQL Server table and it now works. I do need to follow through why my previous package did not work. I think it may have something to do with unicode / non unicode conversation data types failures in the SQL Server table rows which stored the configuration. Of course the reminder to look at the output log, set breakpoints and watch the local variables has helped me make progress. I will update this thread in more detail shortly to avoid anyone else tearing their hair out with this type of issue. If you have found any of my posts helpful then please vote them as helpful. Kieran Wood MCTS BI, PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds

Hi I faced similar issue and did try all options. this link was very helpful since you have mentioned about unicode and non unicode mix up. The issue is basically datatypes of config table should be Nvarchar instead and not varchar. I changed the data type and now everything works normal. Thanks again!