March 14, 2016 at 6:54 am
This one is confusing me a bit. We have a 2008 SSIS package that has been running fine until yesterday. Suddenly it won't send a file via SFTP (using an Execute Process Task). We're aware that there's a strange issue with the powershell script it's trying to run and are working to fix it.
The bigger issue is that when I pull the package down to BIDS with the Protection Level of "Don't Save Sensitive," I'm getting a cryptographic error when trying to run a step right after the Execute Process Task.
The step in question is a File System Task to rename a file. When trying to run that step, I get the error "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."
What's really confusing is when I run a Script Task outside of the container, I don't get this error at all and the task completes successfully.
Why would a File System Task error out on a cryptographic error, but a Script Task work fine? Any thoughts?
March 14, 2016 at 7:04 am
Brandie Tarvin (3/14/2016)
This one is confusing me a bit. We have a 2008 SSIS package that has been running fine until yesterday. Suddenly it won't send a file via SFTP (using an Execute Process Task). We're aware that there's a strange issue with the powershell script it's trying to run and are working to fix it.The bigger issue is that when I pull the package down to BIDS with the Protection Level of "Don't Save Sensitive," I'm getting a cryptographic error when trying to run a step right after the Execute Process Task.
The step in question is a File System Task to rename a file. When trying to run that step, I get the error "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."
What's really confusing is when I run a Script Task outside of the container, I don't get this error at all and the task completes successfully.
Why would a File System Task error out on a cryptographic error, but a Script Task work fine? Any thoughts?
Strange. I think I'd be tempted to open the package in an XML editor and have a poke around ...
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply