We are having some trouble when opening Integration Services packages that contain Execute Package tasks referring to SSIS packages on the server. When developer A last edited such a package, developer B gets errors when he opens the package. The error message is:
Error loading PackageName: 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.
You get one error for each embedded Execute Package task in the package. When developer B makes changes to the package and checks it in, he does not get errors anymore, but now developer A gets the same errors.
We found some information on the topic. There is a MS knowledge base article describing the cause of the problem. It has something to do with the ProtectionLevel property of a package. We also studied the information that is referred to in that KB article.
What we do not understand is why we only have this problem when a package contains Execute Package tasks Can someone explain that to us And is there a best practice for working with Execute Package tasks in an environment where you develop locally (store .dtsx files on the file system controlled by Visual SourceSafe) and deploy to SQL Server
Thanks,
Hans Geurtsen.
Error loading PackageName: Failed to decrypt protected XML node
Hot Topic
- SSIS Data Mapping Summary?
- SqlServer2005 can support merge replication with SqlCe2.0??
- call report with datas updated
- Studio query results returns NULL data as actual "NULL" string
- Nulls when summing a group in an expression
- How to callapse rows together
- SQL SERVER 2005 DATABASE MIRRORING for large number of databases
- TSQL Question - Datetime conversion
- CustomReportItem Installation
- Recursively Calling A Stored Procedure Problem
SQL Server
- Security when dynamically changing data source
- "product level is insufficient" message during flat file import
- Report Authoring Using Report Builder
- SQL Server 2000 DTS Tools Web Download
- How to run an exe in the SSIS scripting task
- ambiguity performance problem
- Split txt file into multiple
- Reporting Services on the Web
- How do a make a bulleted list.
- Privileges for Deploying Reports
Error loading PackageName: Failed to decrypt protected XML node
Yatharth Gupta
Yes, you are on the right track. You need to switch to password-based protection level for the root package.
What we do not understand is why we only have this problem when a package contains Execute Package tasks
The error occurs when the package contains any "sensitive" information that needs to be protected (logins, passwords, etc), in particular case PackagePassword.