SQL Agent job failed

Question

Post reply

SQL Agent job failed

gary1

SSC-Insane

Points: 21152
More actions
January 20, 2010 at 10:16 am

#136651

Hi,
We have SQL Server 2005 Standard edition x64 with SP3. The backup jobs are running fine from years but yesturday, because of power failure server got shut down and later when power is came, servers brought online.
After that the scheduled daily full backup job failed with the below message:
The job failed. The owner () of job Full_Backup does not have server access.
Please advice

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Shree_h Mr or Mrs. 500 Points: 568 More actions · Answer 1

Hi..

Please the the below options...

Rebooting the server once or restart the SQL services.

Try changing the job owner to sa and run the job and change back to original user.

Shree

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 2

Ignacio A. Salom Rangel

SSC-Insane

Points: 20443

January 20, 2010 at 12:00 pm

#1106242

Try restarting the SQL server again.

My blog

Jack Corbett SSC Guru Points: 184394 More actions · Answer 3

Sounds like a user had been removed from the server and owned the job. I'd recommend changing the owner to sa or creating a user just used to own jobs.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

murthykalyani SSCarpal Tunnel Points: 4500 More actions · Answer 4

Jack Corbett (1/21/2010)
Sounds like a user had been removed from the server and owned the job. I'd recommend changing the owner to sa or creating a user just used to own jobs.

If user who owns the job has been removed, then the job should have failed previously before server has got abruptly started.

Also I recommend what Jack has mentioned that change the owner of the job to 'sa' or the service account under which sql server runs.

gary1 SSC-Insane Points: 21152 More actions · Answer 5

Thanks,

It's working when I just reenter the same job owner again (SQLServerAgent->Jobs->Full backup->Properties->General->Job owner-> here, I entered the same user again and ran the job & it's working)

But I did nit understand why the user loose the server access. Because the user is not removed

gary1 SSC-Insane Points: 21152 More actions · Answer 6

I got the same error last night when the server got rebooted?

So every time the server restarts,. I'm getting this issue and to avoid the issue I'm changing the owner (not actually changing, just type the same owner again & say OK)

Please advice how to fix this error permanently

thanks

Seanda.Lucas Grasshopper Points: 15 More actions · Answer 7

I wonder if the user or the user's rights got corrupted when the server restarted. Maybe if you modify the user info or the rights, if it would correct the problem.

I would consider building a new account and assign the job to the new account.

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 8

Have you try what jack adviced you. Changing the user to SA, then check what happens when you restart the server.

My blog

gary1 SSC-Insane Points: 21152 More actions · Answer 9

These are BizTalk related jobs and initially they were cretaed with the owner Btsadmin. Later we changed the owner to Administrator account and it's worked fine and working fine in all other BizTalk servers. But only in this server, I'm getting this error when the server restarts. I'm not sure I can change the BizTalk job owners to SA