February 15, 2012 at 9:13 am
I have created one SSIS package which is having ftp
which pull files from ftp server and save to my local drive
but i'm getting this issue please help.
With same error message I was getting only warning but today job gets failed why ?
please help i'm newbie
Message
Executed as user: cam\Package.Runner. Microsoft (R) SQL Server Execute Package Utility Version 10.0.4000.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:00:00 AM Error: 2012-02-15 10:00:00.61 Code: 0xC0016016 Source: Description: 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: 2012-02-15 10:00:00.62 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Property" 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: 2012-02-15 10:00:33.53 Code: 0xC0029183 Source: Principal Balance File FTP Get FTP Task Description: File represented by "/Concerto/Virtus_Reports/Concerto Principal Balance Report*.pdf" does not exist. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:00:00 AM Finished: 10:00:33 AM Elapsed: 33.088 seconds. The package execution failed. The step failed.
February 15, 2012 at 9:53 am
Sounds like your package has been saved wth 'EncryptSensitiveWithUserKey', and produced by another user.
Try changing the package properties, saving again, and re-running the package.
_____________________________________________________________________
Disclaimer - The opinions expressed by the mouth are not necessarily those of the brain
February 16, 2012 at 12:00 am
You have the protectionlevel of your package probably set to EncryptSensitiveWithUserKey, which is the default. This makes sure only you can open and execute the package without losing sensitive data.
However, the SQL Server Agent operates under another account, thus it cannot decrypt the package contents.
The best option is to set the ProtectionLevel property of your package to DontSaveSensitive.
More info:
Setting the Protection Level of Packages
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 2, 2018 at 11:51 am
I know this posting is a bit old but it's still relevant today (I just experienced the problem).
If you logon to the computer using the service account that runs your SQL server and create the SSIS package under that account, there will be no conflict (error) when the package runs.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply