question

Mrs_Fatherjack avatar image
Mrs_Fatherjack asked

Calling SSIS package from a job

I have an SSIS package that amongst other things programmatically executes a transfer sql server object task. This package runs fine as a package and when called from the cmd line, however it errors when I call it from a job. There are variables I can set to only run bits of the package and it works fine until it gets to the script task that executes the transfer sql server object. I get the following message: > Execution failed with the following error: "The directory 'LocalApplicationData' does not exist.". I've set up a proxy account and made sure that the proxy has bulkadmin and sysadmin priveleges on the server but I can't figure out what else I can do. I also set the account the proxy is set on, which is localadmin, to the job owner. Any ideas gratefully received. Many thanks.
ssissecurityjobproxy
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
siera_gld avatar image
siera_gld answered
The user mapped to the Credential being used in the Proxy account need to have read/write permissions on the fileshare location 'LocalApplicationData'
2 comments
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.