Setting Package protection level

Question

Setting Package protection level

MSSQLBuddy

SSCrazy

Points: 2354
More actions
December 4, 2008 at 10:05 am

#125544

Hi 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 follows
Data 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 time
Error 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 advance
Regards
Nithya
Regards
Priya

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

MarkG Ten Centuries Points: 1237 More actions · Answer 1

Check out a similar post: http://www.sqlservercentral.com/Forums/Topic600005-148-1.aspx#bm613484

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 http://www.JumpStartTV.com - lots of SQL videos there, not just SSIS.

Here's a link to a video about creating a Proxy Account: http://jumpstarttv.com/creating-a-proxy-account_147.aspx?searchid=8597

Hope this helps..

MSSQLBuddy SSCrazy Points: 2354 More actions · Answer 2

Hi,

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 help

Nithya

Regards
Priya

dave-dj SSChampion Points: 11297 More actions · Answer 3

I 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.

_____________________________________________________________________________MCITP: Business Intelligence Developer (2005)

MSSQLBuddy SSCrazy Points: 2354 More actions · Answer 4

Hi,

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.dtsx11"

The connection string is stored in SQL Server as

Data Source=LocalServer;Initial Catalog=MyDB;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;

I have the default package protection level as EncryptSensitiveWithUserKey

Please suggest me a way to solve this issue.Im struggling for the past 2 days....

Thnaks in advance

Nithya

Regards
Priya

dave-dj SSChampion Points: 11297 More actions · Answer 5

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

ConfigurationFilter: Connections

ConfigureValue: Data Source=localhost;Initial Catalog=ssct_dw;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;

PackagePath: \Package.Connections[ssct_dw].Properties[ConnectionString]

ConfigureValueType: String

also, just checking your connection string, i'm not sure if LocalServer for the datasource is valid. Try localhost

_____________________________________________________________________________MCITP: Business Intelligence Developer (2005)

MSSQLBuddy SSCrazy Points: 2354 More actions · Answer 6

Hi,

Thanks for ur reply again...

My values are as follows

Configuration Filter: MyDBSrcConn

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

Nithya

Regards
Priya

MSSQLBuddy SSCrazy Points: 2354 More actions · Answer 7

Sorry.... These are my values stored into SQL Server tables

Configuration Filter: MyDBSrcConn

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

Regards
Priya

SqlServerNinja Ten Centuries Points: 1238 More actions · Answer 8

Hey I have the exact same problem .. Did anyone find a solution yet for the problem.