SSIS scheduled job not running when NOT logged in

[JtheRipper]

Hi there,

I have a strange problem with my scheduled SSIS package.

When I remote desktop into the server using my local windows account user "HOMER\dba", I see my job succeeds (while I am logged in). I can also right click on the job and start it, the job will then run successfully.

BUT, when I log out of the server and wait a while, then log back in I notice that the job failed for the period that I was logged out (job runs every 5 mins), and now that I am logged back in again the job succeeds.

The job owner is "HOMER\SqlSrvAcc". The user is added to the sysadmin server role and relevant SQLAgent*** roles in the msdb database.
The job has only 1 step, and is called "dbaproxy".
There is a credential "dba" with identity "HOMER\dba".

I am no Windows export, but I am thinking my "HOMER\dba" user needs some permissions to be able to run when I am not logged in...

Any advice please?

Thanks,
J.

 

[Catadmin]

First, who owns the actual package?

Secondly, go into BIDS and check your connection managers to make sure they aren't set to run under Windows Authentication. They may be trying to run under the package owner account, which is why it's requiring you to be logged in.

We use a SQL Server Account for our packages because of that issue.

Oh, and lastly, is "HOMER\SqlSrvAcc" a domain user or a local account on the box?



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"