September 4, 2006 at 6:40 am
Do people use integrated auth in SQL 2000, and if so is there an acknowledged problem around losing communication with the domain controller after it has bounced.
Our windows domain controller was down for an hour over the weekend for maint. When I came in on Monday many scheduled jobs had failed and others had run for a long time.
All servers are on SQL2K SP4. The SQL2005 servers had no issues.
This is the sort of message we got:
The job failed. Unable to determine if the owner (DOMXXX\UserYYY) of job JobZZZZ has server access (reason: Could not obtain information about Windows NT group/user DOMXXX\UserYYY'. [SQLSTATE 42000] (Error 8198))
I think I have seen this sort of thing before, and spoke to another DBA who believes that if SQL Server is running any job while the domain controller is down then it goes into a state where it can no longer communicate with the domain controller, even after it comes up again. In this state the SQL service requires restarting.
I have seen similar issues with mail servers - SQL loses touch when the mail server bounces, but in this case sp_stopmail and sp_startmail can usually get it right.
I would like to find out if anyone else has seen this or similar problems?
Thanks,
Renato
September 7, 2006 at 8:00 am
This was removed by the editor as SPAM
September 7, 2006 at 9:58 am
Yes - that is correct. You need to talk to your network guys and add another domain controler in the mix.
I am suprised SQL 2005 did not have any issues. Are you sure that the agent under that is not running under a local account?
September 8, 2006 at 8:44 am
Thanks vik. I will speak to the network guys about a backup domain controller.
Regarding the 2005 machines - they may not have been running jobs at the time.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply