Cryptographic Error in SSIS package

  • Hi All,

    I am getting following error on executing SSIS package through agent job.

    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. Verify that the correct key is available.

    My Scenario is I have changed Windows Server from Work-Group to Domain environment.

    Before making any changes it was working fine, but after putting server in Domain it is giving me above error.

    But when I run this particular SSIS package from BIDS it executes successfully .

    Thanks in Advance.

  • SQLLion (3/10/2014)


    Hi All,

    I am getting following error on executing SSIS package through agent job.

    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. Verify that the correct key is available.

    My Scenario is I have changed Windows Server from Work-Group to Domain environment.

    Before making any changes it was working fine, but after putting server in Domain it is giving me above error.

    But when I run this particular SSIS package from BIDS it executes successfully .

    Thanks in Advance.

    What is the protection level of your package?

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Hi,

    thanks for your prompt reply,

    I have used "EncryptSensitiveWithUserKey" as protection level

  • SQLLion (3/10/2014)


    Hi,

    thanks for your prompt reply,

    I have used "EncryptSensitiveWithUserKey" as protection level

    UserKey is a combination of user and machine related information.

    Basically it means sensitive info is decrypted when only you open the package.

    The problem is that on the server it is a different machine and probably also a different user, so sensitive data cannot be decrypted, hence the error.

    Either change to DontSaveSensitive and store passwords in a configuration, or use EncryptSensitiveWithPassword.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Thanks Koen Verbeeck for your reply and

    Thanks SQLCJ for your helpful link.

    Now I have changed protection level of package to "EncryptSensitiveWithPassword"

    It is working fine on some of my packages, but few packages are giving login failed for user 'xxxx' error on execution.

  • SQLLion (3/10/2014)


    Thanks Koen Verbeeck for your reply and

    Thanks SQLCJ for your helpful link.

    Now I have changed protection level of package to "EncryptSensitiveWithPassword"

    It is working fine on some of my packages, but few packages are giving login failed for user 'xxxx' error on execution.

    Did you supply the password when executing the packages?

    Also, after you've made the change to the new protection level, it's maybe best if you open up the connection managers, fill in the passwords and save them again. Then redeploy the packages.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Thanks Koen Verbeeck,

    I just re-entered the passwords into connection manager.

    That's really work for me.

    Thanks for your all prompt reply. 🙂

  • SQLLion (3/10/2014)


    Thanks Koen Verbeeck,

    I just re-entered the passwords into connection manager.

    That's really work for me.

    Thanks for your all prompt reply. 🙂

    No problem, glad to help 🙂

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply