I have a SSIS package that was migrated from a DTS package. If I rightclick
on the package & click run package within management studio, it executes
correctly. If I run the package in a stored procedure using DTEXEC utility I
get the following error:
Description: 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 t
hat the correct key is available.

I did some searching & came across a KBB article that said it had to do with
the protectionlevel property. I have it set to EncryptSEnsitiveWithUserKey
which is supposed to be the default.
http://support.microsoft.com/default...b;en-us;904800

Anyone come across this error before & have a resolution?

Thanks for the help!
John

Hello John D.,

To quote from the KB - "...when a different user account or a different computer
is used to run the SSIS package, the EncryptSensitiveWithUserKey value of
the ProtectionLevel property is engaged, and the Password property of the
SSIS package remains encrypted. When this occurs, an error message is generated."

"To resolve this behavior, change the value of the ProtectionLevel property
in the SSIS package." - So change it from the default of EncryptSensitiveWithUserKey
to something which is not tied to a specific user.

You do not develop under the same user account as would be used by the stored
proc from SQL, so the decryption fails.

Darren,
Thanks for the reply but I have tried the other protectionlevels. I used
the one where you set a password. In my SP, I passed the password along to
the dtexec utility & received the same error. I didn't try the one with no
protection but doesn't that mean that passwords will be stored as they are
typed in & not encrypted which would not be secure, correct? Or am I
interpretting it wrong?

THanks,
JOhn

"Darren Green" wrote: