November 2, 2012 at 7:33 am
I'm using SQL Server 2012 Enterprise Build 11.0.2100. I have about 200 packages that move data between servers...typical ETL. Sometimes a package will fail to execute and throw the following error:
"Error 0xC0014061 while executing package from project reference package "xxxxx.dtsx". The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the destination supports secure storage capability.
The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the destination supports secure storage capability."
This error is intermittent. It is not related to a single package and does not always error on the same package.
My packages are deployed using the package deployment model.
It seems that I have no control over the Protection Level set for the packages because when I import the package back into SSDT, all the package configurations are set to EncryptSensiveDataWithUserKey instead of ServerStorage.
I've tried to set all 200+ packages to server storage and deploy but that didn't help.
There is a step in the deployment process that changes the ProtectionLevel of the packages...does this set it to EncryptSensitiveDataWithUserKey because the catalog is encrypted or is this done by the import wizard? Has anyone ever ran into this before and how do I fix it?
November 15, 2012 at 9:35 am
Posting this here...knowledge is wealth.
I tried to start different packages simultaneously and started receiving dead-lock errors.
I finally found a solution to the dead lock issue and my original post after stumbling across this KB:http://support.microsoft.com/kb/2699720
After staggering the start of the packages I am not longer receiving weird protection errors or dead-lock errors. I wish someone would tell me how they are related but I am delighted I've found something! We are planning to install SP1 quick, fast and an a hurry within the next week...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply