Issues with SSIS in named instance SQL 2014

Question

I have a SSIS job that runs without any issues with native mode. But for named instance, I get these errors:
Any suggestions?
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.  End Error  Error: 2015-04-22 15:20:01.67     Code: 0xC0016016    
Source: xxx Description: Failed to decrypt protected XML node "OraPassword" 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.  End Error  Error: 2015-04-22 15:20:02.22     Code:
0x000002BD     Source: xxx  Connection manager "yyy"     Description:Oracle Home not found.  End Error  Error: 2015-04-22
15:20:02.22     Code: 0x0000020F    Source: mmm[96]    
Description: The AcquireConnection method call to the connection manager yyy failed with error code 0x80004005.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.  End Error 
Thanks

Answer 1

Hi LaxUdas,
If I understand correctly, the package is developed with Protection Level set as "EncryptSensitiveWithUserKey". When you execute the package via a SQL Agent Job in a Named Instance, the account that job step using is not the user that create the
package. So it cannot be able to connect to the Oracle DB with invalid connection string.
This behavior is by design. In an Integration Services package, the following information is defined as sensitive:
The password part of a connection string.
The task-generated XML nodes that are tagged as sensitive.
Any variable that is marked as sensitive.
EncryptSensitiveWithUserKey uses a key that is based on the current user profile to encrypt only the values of sensitive properties in the package. Only the same user who uses the same profile can load the package. If a different user opens the package,
the sensitive information is replaced with blanks and the current user must provide new values for the sensitive data.
To work around this issue, please refer to the following suggestions:
Change the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword. This setting uses a password for encryption. To open the package in SSIS Designer (SSDT), the user must provide the package password.
Change the Named Instance SQL Agent Service account to the user that create the package, like your Default Instance.
Use SSIS Package configuration files to store sensitive information, and then store these configuration files in a secured folder. You can then change the ProtectionLevel property to DontSaveSensitive so that the package is not encrypted and does not try
to save secrets to the package. When you run the SSIS package, the required information is loaded from the configuration file. Make sure that the configuration files are adequately protected if they contain sensitive information.
The following two documents are for your references:
https://msdn.microsoft.com/en-us/library/ms141747.aspx
https://support.microsoft.com/en-us/kb/918760
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support