SSIS package execution fails from the integration services catalogue - Failed to decrypt an encrypted XML node.

Raj T 21 Reputation points
2023-01-20T14:50:30.1366667+00:00

Hi,

I've migrated SSIS packages from SQL 2014 to SQL 2019. 

Software and tools used in the VM:

Visual Studio 2019

SQL Server 2019

SQL Server Integration Services 15.0

Microsoft Connector for Oracle (SSIS Oracle connector) 15.0

And use Standalone SQL Server Integration Service (SSIS) DevOps Tools version 1.0.0.0 - SSISBuild.Exe to build SSIS project and deploy using MSBuild.exe to the SSISDB.

After the successful deployment, I get the below message during execution from the integration services catalogue.

Error:

Failed to decrypt an encrypted XML node because the password was not specified or not correct. Package load will attempt to continue without the encrypted information.

The protection level of the package requires a passord, but package password property is empty.

I am getting this error even after setting the protection level to 'EncryptSensitiveWithPassword' on both the project and package levels with the same password.

Any suggestions would be appreciated.

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,702 questions
Community Center Not monitored
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Yitzhak Khabinsky 26,586 Reputation points
    2023-01-20T21:16:20.6366667+00:00

    Hi @Raj T,

    Please try to change your SSIS project ProtectionLevel setting value as DontSaveSensitive.

    You can read about it here: https://www.mssqltips.com/sqlservertip/2091/securing-your-ssis-packages-using-package-protection-level/

    SSIS - ProtectionLevel

    1 person found this answer helpful.
    0 comments No comments

  2. ZoeHui-MSFT 41,491 Reputation points
    2023-01-23T02:34:52.0933333+00:00

    Hi @Raj T,

    To protect the data in an Integration Services package, you can set a protection level that helps protect just sensitive data or all the data in the package.

    Set your protection level to DontSaveSensitive may resolve the issue.

    Also check:Access Control for Sensitive Data in Packages

    Regards,

    Zoe Hui


    If the answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

  3. Raj T 21 Reputation points
    2023-01-27T15:18:24.04+00:00

    Thanks for your reply. I can execute it after changing the protection level to 'DontSaveSensitive', but I don't know why we can't implement this with the protection level of 'EncryptSensitiveWithPassword'.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.