![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I migrated a DTS package from SQL2000 to SQL 2005 , when i try to run it using a stored procedure I get this error. Description: Failed to decrypt protected XML node "DTS:Password" 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. Even when i am logged in as 'sa' I still get the same issue. |
#3
| |||
| |||
|
|
Hello Ram, Ok so this error is telling you that something sensitive in the package has been encrypted. It does this because of the ProtectionLevel property of the package. Passwords are favourites and the ExecutePackage task PackagePassword property is by default Sensitive. The default for the ProtectionLevel is EncryptSensitiveWithUserKey which means that unless the same user fires the package as created it then the sensitive info will not be decrypted. Set the ProtectionLevel on the package to DONTSAVESENSITIVE and handle the sensitive stuff through Configurations Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com I migrated a DTS package from SQL2000 to SQL 2005 , when i try to run it using a stored procedure I get this error. Description: Failed to decrypt protected XML node "DTS:Password" 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. Even when i am logged in as 'sa' I still get the same issue. |
#4
| |||
| |||
|
|
Hello Ram, Ok so this error is telling you that something sensitive in the package has been encrypted. It does this because of the ProtectionLevel property of the package. Passwords are favourites and the ExecutePackage task PackagePassword property is by default Sensitive. The default for the ProtectionLevel is EncryptSensitiveWithUserKey which means that unless the same user fires the package as created it then the sensitive info will not be decrypted. Set the ProtectionLevel on the package to DONTSAVESENSITIVE and handle the sensitive stuff through Configurations Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com I migrated a DTS package from SQL2000 to SQL 2005 , when i try to run it using a stored procedure I get this error. Description: Failed to decrypt protected XML node "DTS:Password" 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. Even when i am logged in as 'sa' I still get the same issue. |
#5
| |||
| |||
|
|
Allan, I did try with the new setting for ProtectionLevel as "DONTSAVESENSITIVE" ,but it still throws up the same error. Yes I am running the package as a different user. -Ram "Allan Mitchell" wrote: Hello Ram, Ok so this error is telling you that something sensitive in the package has been encrypted. It does this because of the ProtectionLevel property of the package. Passwords are favourites and the ExecutePackage task PackagePassword property is by default Sensitive. The default for the ProtectionLevel is EncryptSensitiveWithUserKey which means that unless the same user fires the package as created it then the sensitive info will not be decrypted. Set the ProtectionLevel on the package to DONTSAVESENSITIVE and handle the sensitive stuff through Configurations Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com I migrated a DTS package from SQL2000 to SQL 2005 , when i try to run it using a stored procedure I get this error. Description: Failed to decrypt protected XML node "DTS:Password" 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. Even when i am logged in as 'sa' I still get the same issue. |
![]() |
| Thread Tools | |
| Display Modes | |
| |