Friday, March 23, 2012

Failed to decrypt protected XML node

Failed to decrypt protected XML node ... blah blah.

Looks familiar, right?

Package Protection mode is : EncryptSensitiveWithPassword

Package runs fine from within BIDS. Close package. Open package - asks for password. So far so good.

When running from command prompt with:

dtexec /File "C:\Program Files\Microsoft SQL Server\90\DTS\Packages\MyPackage.dtsx" /De mypassword

Get that cryptography error.

Doesn't happen for other packages... what can I be doing different/wrong?

Thanks,
NiteshDoes your password contains any of the following:
a) space characters - use the format /De "your_password"
b) punctuation characters - use the format /De "your_password"
c) " - double any "
d) ; - use the format /De "\"your_password\""

Hope this helps

Regards,
Ovidiu Burlacu|||

Ovidiu Burlacu wrote:

Does your password contains any of the following:
a) space characters - use the format /De "your_password"
b) punctuation characters - use the format /De "your_password"
c) " - double any "
d) ; - use the format /De "\"your_password\""

Hope this helps

Regards,
Ovidiu Burlacu

Nopes.
Password is same as that for other packages, all lowercase alphabets, 8 characters.

thanks,
Nitesh|||

Since your protection is only EncryptSensitiveWithPassword then only sensitive information will be encrypted, and my guess is that this package has been encrypted with a different password (mistyping).

Can you try to open package in BIDS and then go to View -> Error List and see if the same error has been posted?

I'm guessing that the same error happens in the designer, but we should not fail open the package just because we cannot retrieve the Password in a ConnectionString, so instead we post an error.

HTH,
Ovidiu Burlacu

No comments:

Post a Comment