July 16, 2009 at 8:05 am
What would cause my SQL Scheduled job to fail with the error: Login failed for user ''. ?
It only happens intermittantly. It's ok for a week, then fails. It's a job that can be run multiple times, so I thought maybe it's a network hiccup of some sort, so I scheduled it to run at 3 am, 3:05, 3:10, and 3:15, thinking that it should work at least once. Yesterday it failed 2 out of 4 times. Today it failed all 4 times ?
It's running under a windows domain account with sql admin permission.
Also, although the job failed, I'm not getting a failure email. I've tested email notifications for the same operator with another job and that part seems fine. Does a login failure not trigger a notification ?
Where should I look ? Thoughts ?
July 16, 2009 at 8:12 am
Is the job owner yourself? Try change it to NT AUTHORITY\SYSTEM, and that should fix the problem.
July 16, 2009 at 8:48 am
No, I'm not the owner. It's a Windows account that's used across servers in many places without issue except in this one case.
July 16, 2009 at 12:32 pm
homebrew01 (7/16/2009)It's running under a windows domain account with sql admin permission.
My money is on a network issue that prevents authentication.
How about using a local account?
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.July 16, 2009 at 12:46 pm
Try to put the sa account like owner of the job 🙂
July 16, 2009 at 2:22 pm
Juan Pablo (7/16/2009)
Try to put the sa account like owner of the job 🙂
:blink: why would you nuke them when an infantry brigade would suffice?
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.July 17, 2009 at 9:18 am
Can you check to see if the job is failing because your servers resources (memory, disk or CPU) are maxing out. I found with intermittent problems it is usually a system resource issue - that is why sometimes it works and other times it does not. Start taskman then run the job.
July 17, 2009 at 10:43 am
PaulB (7/16/2009)
Juan Pablo (7/16/2009)
Try to put the sa account like owner of the job 🙂:blink: why would you nuke them when an infantry brigade would suffice?
hmm ... so the windows account is sysadmin .... and you wouldn't want to replace that with sa ??
We generaly don't use windows accounts as job owners !
(because of legacy authentication on SQL2000 !!)
If a job needs other resources than the local server, we use a proxy account to be used with that jobstep. That proxy windows account will get granted the auth it needs.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply