We have an issue where we create ssis packages on the database server (on a sql cluster), create a job via the agent to run it and it works fine.
However, if we create the job on the application server using the sqlserver management tools via the agent, the job fails every time.
This is also the case if we use BIDS from the app server to create the package and then try to set up a job to run it.
We have tried setting up proxy users and giving them relevant permissions in the credntials that they are attached to in order to run the job but still no success.
It is set up to use windows authentication, yet we get a message in the job log saying bad username or password?
The job runs under the sql.service account which belongs to the sql agent I believe.
Has anyone else come accross this issue and found a solution
