title: Why does my SSIS package fail with filesystem permission error when run from the Integration Services Catalog
body: <p>I have an SSIS package that accesses a folder on a network share.
  If I run this package as part of a SQL Agent Job, it succeeds.
  If I run this package directly from the SSIS Integration Catalog (Right Click and execute) on my development PC, it fails with a permission error .
  If I run this package directly from the SSIS Integration Catalog (Right Click and execute) on the server hosting the SQL instance, it works.</p>
  
  <p>All users's involved in this process have access to the folder (my username, the user setup to run the SSIS service and the SQL Agent service). I know this for sure because I can accsess the folders logged in under any of these users.</p>
  
  <p>Any ideas why this would be?</p>
  
  <p>What baffles me is that it works if you run it from the server hosting the SQL instance, but not from my local PC (when logged in under the same user)!</p>
  
  <p>We've gotten to the point that when we want run certain packages that access the file system, we create an SQL agent job to run it. It's not ideal.</p>