Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

package protection issue failed to decrypt protected xml node Expand / Collapse
Author
Message
Posted Wednesday, January 13, 2010 8:56 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 2:13 PM
Points: 406, Visits: 963
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
Post #846967
Posted Thursday, January 14, 2010 8:18 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 2:13 PM
Points: 406, Visits: 963
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.
Post #847588
Posted Thursday, January 14, 2010 8:19 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 2:13 PM
Points: 406, Visits: 963
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.
Post #847590
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse