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? Has anyone ever ran into this before and how do I fix it?
*edit*
I was wondering if this had to be related to my destination provider. I'm currently using OLE DB\SQL Server Native Client 11.0 and this package is being ran from a SQL Server Agent job. Could this be a simple permissions issue or should the change providers for my data flow tasks?