I have been racking my brain with this one all morning.
My problem is that I have an SSIS package which moves files from a remote folder to my local server using a file-system-task.
The folder is mapped using NET USE and I can access the files fine. When I manually run the SSIS package in BIDS all is ok and the files move to the server. When I schedule this package it succeeds however no files are moved (There are no errors in the job history).
I am using an SSIS proxy with domain credentials for the server not the remote folder. The remote drive has different domain details (I think this might be the problem).
The package is deployed using SSIS catalog and using SS2012.
Any help would be really appreciated.
asked Feb 05, 2014 at 10:40 AM in Default
Right. Proxies were failing for me however this link solved it for me.
I created an "Execute Process Task" to map the drive before pulling the files.
I don't think this is a long term solution however it fixes my immediate issue.
Thanks for the help all.
answered Feb 07, 2014 at 09:39 AM
Can you try a different source (on the domain, where you can be 100% certain that permissions are correct) and see if you have the same issue? Alternately, can you temporarily alter the security on the remote location to be EVERYONE allowed and test? This will show if the location and it's applied security settings are the problem.
answered Feb 05, 2014 at 02:58 PM
Can you change the proxy account with your credentials(as you are able to manually run the package) and see whether it is working ? Try to create another domain account (which you have mentioned having access to drive) as a proxy and try ? I feel that there is some issue with the proxy account you have configured for that path.
answered Feb 06, 2014 at 04:16 AM