InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 13:59:20 GMT20http://www.sqlservercentral.com/Forums/Topic613887-148-1.aspxHey I have the exact same problem .. Did anyone find a solution yet for the problem.Thu, 07 Mar 2013 09:30:09 GMTSqlServerNinjahttp://www.sqlservercentral.com/Forums/Topic613887-148-1.aspxSorry.... These are my values stored into SQL Server tablesConfiguration Filter: MyDBSrcConnConfiguredValue : Data Source=ARC_NITHYA;Initial Catalog=MyDB;Provider=SQLOLEDB.1;Integrated Security=SSPI;Auto Translate=False;Package Path : \Package.Connections[OLEDBProviderSQLServerMyDB].Properties[ConnectionString]Configured Value Type: StringFri, 05 Dec 2008 06:09:17 GMTMSSQLBuddyhttp://www.sqlservercentral.com/Forums/Topic613887-148-1.aspxHi,Thanks for ur reply again...My values are as followsConfiguration Filter: MyDBSrcConnConfiguredValue : Data Source=LocalServer;Initial Catalog=MyDB;Provider=SQLOLEDB.1;Integrated Security=SSPI;Auto Translate=False;Package Path : \Package.Connections[OLEDBProviderSQLServerMyDB].Properties[ConnectionString]Configured Value Type: StringNithyaFri, 05 Dec 2008 06:08:01 GMTMSSQLBuddyhttp://www.sqlservercentral.com/Forums/Topic613887-148-1.aspxwhat does the rest of the configuration table look like?as an example, this is the value for each column in my config table for a connection:[b]ConfigurationFilter: [/b]Connections[b]ConfigureValue: [/b]Data Source=localhost;Initial Catalog=ssct_dw;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;[b]PackagePath: [/b]\Package.Connections[ssct_dw].Properties[ConnectionString][b]ConfigureValueType: [/b]Stringalso, just checking your connection string, i'm not sure if [b]LocalServer[/b] for the datasource is valid. Try [b]localhost[/b]Fri, 05 Dec 2008 05:55:02 GMTdave-djhttp://www.sqlservercentral.com/Forums/Topic613887-148-1.aspxHi,Thanks for ur reply. The problem exists still. I changed a package configuration for SSIS to XML file. it worked fine for the first time. I closed and reopen in BIDS... I got the following package loading error"Error loading Package.dtsx: The connection string format is not valid. It must consist of one or more components of the form X=Y, separated by semicolons. This error occurs when a connection string with zero components is set on database connection manager. E:\TestPackConfFromXML\Package.dtsx 1 1 "The connection string is stored in SQL Server asData Source=LocalServer;Initial Catalog=MyDB;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;I have the default package protection level as EncryptSensitiveWithUserKeyPlease suggest me a way to solve this issue.Im struggling for the past 2 days....Thnaks in advanceNithya Fri, 05 Dec 2008 05:43:51 GMTMSSQLBuddyhttp://www.sqlservercentral.com/Forums/Topic613887-148-1.aspxI might be misunderstanding this, but have you configured your package configurations in SSIS to connect to SSIS directly?To use package configurations successfully, you will need to set a connection to the SQL server via:- an environment variable- an xml file or a registry entry.I think it's pretty common to use an XML configuration file.Once you have this configured, you can setup you other package configurations using a configuration table in your SQL server db that you defined in the XML file.Fri, 05 Dec 2008 04:19:10 GMTdave-djhttp://www.sqlservercentral.com/Forums/Topic613887-148-1.aspxHi,Let me give a brief description of my error. The scenario in ur post explained the package error when deployed from SQL Server agent. My scenario is that The package configurations are from SQL Server.(Both SSIS and the SourceDatabase).When i run the package for the first time after creating it in BIDS, it runs successfuly.When i close the package and reopen it for the second time in BIDS, i get the package loading error as mentioned in the previous post. My doubts are .......1. Can we have both the SSIS and the source database connection strings in to the same table (SSIS Configurations) in SQL Server? 2. Does the package protection level has impact on SQL Server connection strings....?3. Should i want to change connection managers?Please helpNithya Fri, 05 Dec 2008 03:20:23 GMTMSSQLBuddyhttp://www.sqlservercentral.com/Forums/Topic613887-148-1.aspxCheck out a similar post: [b]http://www.sqlservercentral.com/Forums/Topic600005-148-1.aspx#bm613484[/b]I haven't done the deployment into SQL Server (using filesystem instead) but sounds like you could benefit from using a Proxy Account & Credentials. See the link in the above post regarding a how-to video by Brian Knight at www.JumpStartTV.com - lots of SQL videos there, not just SSIS.Here's a link to a video about creating a Proxy Account: [b]http://jumpstarttv.com/creating-a-proxy-account_147.aspx?searchid=8597[/b]Hope this helps..Thu, 04 Dec 2008 15:56:42 GMTMarkGhttp://www.sqlservercentral.com/Forums/Topic613887-148-1.aspxHi All,I have setup the package configurations(for both source database and the SSIS database) from SQL Server table, as they dnt have access to create Environment variable in the prod server. I'm using OLE DB connection --> Native OLEDB\SQL Native Client as the connection manager.I have the connection strings stored as Data Source=server1;User ID=abc;Initial Catalog=MyDB;Provider=SQLNCLI.1;Persist Security Info=True;Auto Translate=False;I updated the password manually as followsData Source=server1;User ID=abc;Password=123;Initial Catalog=MyDB;Provider=SQLNCLI.1;Persist Security Info=True;Auto Translate=False;The package protection level is ENCRYPTSENSITIVEWITHUSERKEY.The package gets the following error once it is reopened for the second timeError loading Package.dtsx: The connection "server1.MyDB.abc" is not found. This error is thrown by Connections collection when the specific connection element is not found. E:\Package.dtsx Please help me in resolving this issue as i m struggling for more than a day.Thanks in advanceRegardsNithyaThu, 04 Dec 2008 10:05:36 GMTMSSQLBuddy