SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


package protection issue failed to decrypt protected xml node


package protection issue failed to decrypt protected xml node

Author
Message
Tom Van Harpen
Tom Van Harpen
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2342 Visits: 1115
We have a package that executes other packages. When opening the solution in BIDS we get, "failed to decrypt protected xml node for package password", for each package that is called from the parent.
All packages are set to don't save sensitive so I don't understand why this is an issue.
There are 2 developers working on this and my feeling is once one works on it the other gets the errors and vise versa.
I'm guessing there is a cert or key that needs to be loaded on each machine / server that accesses or executes the packages.
Any help correcting this would be appreciated. thx
Tom Van Harpen
Tom Van Harpen
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2342 Visits: 1115
I have a resolution on this topic. The problem was not with the packages being called, it was the calling package that that had save sensitive with user key. It was trying to access the package passwords for each package it was calling and could not since there was no user key specified. I changed the parent package to also be "Don't Save Sensitive" That was the problem.
Tom Van Harpen
Tom Van Harpen
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2342 Visits: 1115
In addition the called packages didn't fail since there never was a password to decrypt. Had there been package passwords set for the child packages within the Execute Package Task the calls would have failed, but as it was the child packages did not require a password.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search