Let me start by saying I have spent several hours searching this forum and the web for a solution to our specific issue and have not been able to find anything that is specific to our issue - most of what I've seen is issues once the package is deployed to the server, not vice-versa. So I'm going to try my first post here and see how it goes. How we normally opertate: We develop and test our SSIS packages on our local machines, and then deploy them using MSSQL Integration Services to the particular database server. When we deploy the SSIS packages, they are deployed with Protection Level set to 'Reply on server storage and roles for access control'. What varied: Our must current version of a specific SSIS package got wiped out on my local machine after it was deployed to Integration Services but before it was able to be checked into Team Foundation Server. In order to get the latest version of the package, I exported the package from Integration Services. I selected the Package Location as 'File System', set the Protection Level to 'Encrypt sensitive data with user key', and set the Package path to a location on my local machine. When I run this package on my machine from within Visual Studio, I get the following error message as the package is starting: "Error at ImportDropShipInventoryData [Log provider "SSIS log provider for Text files"]: The SSIS logging provider has failed to open the log. Error code: 0x80070522. A required privilege is not held by the client. (Microsoft.DataTransformationServices.VsIntegration)" I then removed logging from the SSIS package and ran the package again. The package hung at it's first component and finally returned a similar error "A required privilege is not held by the client." The account I am executing the package from in Visual Studio is a local admin on the machine I am running it on. Has anyone ran into this before or know what I need to do to get this package to run? I've tried changing the package protection level of the package in Visual Studio and nothing seems to work. Thanks for any help you can provide.

My guess is that because this package security was say EncryptSensitiveWithPassword you need to change it back to the exact matching security setting and use the proper password. Can you try to export using this setting?Arthur My Blog

Arthur, Thanks for the response. Unfortunately, there was no password. When we deployed, we set the protection level value to 'Rely on server storage and roles for access control'. During the export process, when you select the Package Location type 'File system', the option for the Package Protection Level does not include 'Rely on server storage and roles for access control'. With file system, I only have the options of: (1) Do not save sensitive data (2)Encrypt sensitive data with user key (3) Encrypt sensitive data with password (4)Encrypt all data with user key (5)Encrypt all data with password. What's odd is that when I do the export, I am logged into the Management Studio under the same credentials I am running the Visual Studio under. I'm a seasoned C++ and C# programmer but am not nearly as experienced in SQL Server and Intergation Services, so I'm a little out of my comfort zone with some of these more advanced issues.