April 30, 2007 at 3:35 pm
I have a situation here where members of the sqlagentoperator role is getting false failures on a SQL agent job. If they start the job manually, it comes back quickly saying the job fails, however, if they look in job history, it shows the job as running and it completes successfully after the expected run time of 20 minutes. If a member of SA starts the job, they do not get the failure at all. Has anyone else run into this behavior?
May 1, 2007 at 11:17 am
The SQLAgent job has an owner, and this is checked before the job can be started.
inidividual jobsteps can have a workflow to other steps in the same job
- eg step 1 on success goto step 2, on fail goto step 9
there could also be complexity with MSX/TSX [federation of servers executing jobs]
I would be tempted to find a quiet mement to stop+restart the SQLAgent service and see if the problem goes away. Are you on latest Service Packs etc ?
May 3, 2007 at 11:10 am
no, we are still on 2005 sp1. I'll try and restart the agent and see if that helps - thanks
May 3, 2007 at 12:56 pm
It is not related to service pack version but context when a system admin runs the job it runs in the context of the system admin, but when others runs the jobs it runs in the context of the Agent which in some cases needs admin level permissions. So create an admin level service account to use to create proxy account to run the jobs. Run a search for Agent proxy account in the BOL. Hope this helps.
Kind regards,
Gift Peddie
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply