Deployed SSIS package has access denied to file directories and work fine in VS

Question

Deployed SSIS package has access denied to file directories and work fine in VS

Apostolu, Chris 0

I’ve tested a couple of things out with different packages that have been deployed to SQL Server. I noticed that within the same package, I can have a script task which fails to connect to a file directory but I don’t have an issue with connecting a flat file data source task to the same directory. If I use a flat file destination task, that fails also. It sounds like something doesn’t have full permissions because the flat file source task just reads the file without issue. I run this in VS and there are no problems. when I check the logs of the deployed package it shows my id as the Executed As Name and the Caller Name. The network guys say that the ids being used have read/write access.

0 comments

1 answer

Your answer

Answer 1

Deepesh Dhake 85

It looks like the pattern you're describing is most likely a Kerberos double-hop issue rather than a permissions one.

When the package runs on the SSIS Catalog, your credentials reach the SQL Server but aren't forwarded on to the file share. So the connection arrives there as the SSIS service account, not as you even though the SSISDB log shows your ID as the Executed As Name. That's why your account has access but it still fails.

To confirm, you can have your Script Task log that shows the actual identity hitting the share.

A quick test is to grant the SSIS service account read/write on the share. If that fixes it, the longer-term options are running the package through a SQL Agent Proxy account that has share access, or configuring constrained Kerberos delegation with help from your AD team.

Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator

2026-06-04T04:34:40.0466667+00:00

Hi @Apostolu, Chris ,

In addition to the excellent points already mentioned regarding Kerberos delegation, it may also be worth confirming how the package is being executed (SSIS Catalog, SQL Agent Job, DTExec, etc.) and which account is actually reaching the file share.

The behavior where a Flat File Source can read from the directory while a Script Task or Flat File Destination encounters access denied errors suggests that different components may be running under a different security context or that write permissions are not being applied to the account ultimately accessing the share.

If the OP returns, it would be helpful to know whether the target path is a UNC path and whether the SQL Agent/SSIS service account can manually create a test file in the same location. That information would help confirm whether the issue is related to the execution context rather than the package itself.

Thanks,
Akhil.
Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator

2026-06-08T05:11:34.33+00:00

Hi @Apostolu, Chris ,

Just following up to see if you were able to identify the account under which the package is executing and whether any permission changes resolved the issue.

If the problem persists, an update on the execution method and any additional error details would be helpful. Knowing whether the failure occurs consistently across all deployed packages or only with a specific package could also provide additional clues.

Please let us know the current status when you have a chance.

Thanks,
Akhil.

Share via

Deployed SSIS package has access denied to file directories and work fine in VS

1 answer

Your answer