user3460848
user3460848

Reputation: 63

Why getting an access to file path denied message when executing ssis package from catalog

I've gone through a number of posts - and haven't come across a solution to this. I've spent days on this... I have a project which contains one package with parameters that as part of the processing, moves files from file server to db server & vice versa. It runs fine on ssdt. I deployed it to SQL Server 2012 ssisdb using project deployment. Before doing this, I mapped parameters to configuration values on the ssdt side, and it appears that I can use these on the server, so saw no need to set up environment variables for (yet). When I execute the package via ssms on the server, I get 'Access to the path ... is denied'. My understanding is that the package will execute using my credentials (since I'm using mine on ssms) -- and, as I said previously, this was working fine with my credentials on ssdt. I've checked permissions on the file and the share. I've confirmed that I am added to the Dcomcnfg - security - Launch and Activation Permissions.

Upvotes: 1

Views: 10075

Answers (2)

GOZ_91
GOZ_91

Reputation: 21

Realise this is super old thread; but I've been running into this issue all day today. The SSMS history error log states that the job is being run as "NT Service\SQLSERVERAGENT" (at least in my case). I've added SQLSERVERAGENT to local admins group and rebooted server (I'm sure just retsarting the SQL Server Agent would have worked too).

Upvotes: 2

user3460848
user3460848

Reputation: 63

When I re-started ssms this morning as administrator, the package ran successfully without the 'Access to the path ... is denied' error . I confirmed that I would get the error otherwise.

Upvotes: 2

Related Questions