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/
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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/
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.
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'.