Hi all,
I hope someone can help me, I have hit a brick wall :(
I have set up an SSIS package on one of my servers [Server A] which extracts data from a 3rd party server [Server B] (I have SQL authentication to that server as it isn't mine and it is all that it available), the package then does some work on the data itself then dumps that data on another one of my own servers [Server C] (Windows authentication, full admin rights etc).
Because of existing processes and systems I have to use Server A to run the job to transfer the data between B & C.
The package runs fine when I run it from Server A, which I have done as running it as a plain file through Visual Studio, and I have also uploaded the package to the integration services of Server A and ran it from there manually no problem.
The issue I have is when I set the package up to run as a scheduled job within Server A. The job is set to run the package using a proxy account which has Admin access on Server C to dump the data, but for some reason it keeps failing and I am sure it is something to do with getting the data from Server B, (at a guess - it's like the job is trying to use Windows authentication instead of the SQL authentication which I have saved within the package?!).
I have read various other posts and tried changing the security level on the package to 'with password' then use the /DECRYPT extension on the job, but it makes no difference and I still get the same error (which is unfortunately very little as the job history tells me nothing apart from what step it failed on)
Have I missed some blindingly obvious option somewhere as to why it doesn't work using the proxy account? For testing purposes I wanted to use a process of elimination to find what the problem was and I created similar jobs that just dumped data onto server C using a job on Server A and this scheduled job worked fine.
I then did a scheduled job that did nothing apart from extract data from server B and it failed again, so it really does seem like the proxy account just isn't utilising the SQL authentication I have saved in the package but I don't know why.
If anyone has any advice I would appreciate it!
Thanks