Ssis error failed to decrypt protected xml node

Sign in to vote. Wednesday, August 1, AM. Hi Surendiran, This is because the package has been created by somebody else and the package is being deployed under sombody else's account. As a solution: Either you have to set up the package in SQL server under your account which some infrastructures do not allow. OR Set the package property Protection Level to " DontSaveSensitive " and add a configuration file to the package and set the initial values for all the variables and all the connection manager in that configuration file which might be tedious of-course.

OR The third options which I like do is to open the package file and delete the password encryption entries from the package. Hope this helps. Please mark the post as answered if it answers your question. Wednesday, August 1, PM. Reopen the package and verify that the error has disappeared.

This will restore the encryption of the sensitive data using your User Key. Repeat Steps 2 and 3. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: The package execution failed. The step failed. Sounds like your package has been saved wth 'EncryptSensitiveWithUserKey', and produced by another user.

You need to look at the issues related to ProtectionLevel and determine the best way to address it. Office Office Exchange Server. Not an IT pro? Script Center. Sign in.

United States English. Ask a question. Quick access. Search related threads.