Got a multi package project that is working well on one machine, Now I want to move it to another (both running the June CTP)
I copied all the files but when I open it I get:
Error 8 Error loading NPRImport.dtsx: Failed to decrypt protected XML node "PackagePassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. c:\documents and settings\administrator\my documents\paulsvisual studio\projects\data transformation project4\data transformation project4\NPRImport.dtsx 1 1
What has to be changed before this works Is this a server setting issue, a package issue I get about 10 errors almost identical
Is there like a checklist of steps to go through to make packages transportable
Paul Pisarek
Trying to move a package to a new server
Hot Topic
- AS2005 Cube Processing
- How to drop users programmatically through a sp
- problem in creating database and table in one shot
- Report Corruption When Exported to Excel
- Flat File data for every row
- HTML rendering with Reporting service
- SSIS Access from SQL Server Management Studio
- Help with ##table
- Attribute Relationships
- Newbie question about indexes
SQL Server
- ODBC Destination in SSIS
- Strange cube processing error
- SQLCLR no Database projects in VS2005 projects list -?
- DTS SQLStatement: Unable to update dynamically
- Percentile
- How do i watch variable values during debugging ?
- Making our SQL Server 2000 application ready for SQL Server 2005
- OLAP cube in MS analysis server using data from oracle database
- Export the data as an XML file?
- Writting multiple rows from one input Row
Trying to move a package to a new server
Bobmmp
You can change this by selecting the ProtectionLevel on the package properties in the designer properties grid.
Optionally, when you import the packages into SQL Server, the Import Package dialog gives you the option to change the protection level as well. This is the only time you'll be able to change the protection option to ServerStorage.
playpiano
I use the EncryptSensitiveWithUserKey protection level.
When the error happen, I have no other choice than going through every single connection and re-type the password. In my case, 90 packages with up to 10 connections in each.
I do not deserve this punishment.
Is there any way to simply copy paste the userkey to another server Note that my packages uses config files for the connections including the passwords so I can run them with an application account in SQL Agent but still, I get the error.
I feel like I am completely mis-understanding this security process. Is there any clear and simple "How-to" guide to create ssis packages that you can move accross servers and execute with a service account in SQL Agent and keep up when you change your password and which does not recquire any password to open
Thanks
Philippe
Quendi
One issue I had to figure out was when moving packages that have been deployed and use a Config file, you have to reinstall the package with the DTS installer, you can't just copy the packages. The reason is, the deployed package contains the absolute path to the config file, so you'd have to modify the contents of the .dtsx file.
Not sure if this is relevant here, but I figured it was worth sharing