BUG: Starting the SQL Server Agent is Unsuccessful on a Backup Domain Controller (320338)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions) SP1
- Microsoft SQL Server 2000 (all editions) SP2
- Microsoft SQL Server 2000 (all editions) SP3
This article was previously published under Q320338 BUG #: 356936 (SHILOH_BUGS) SYMPTOMS Starting the SQLServerAgent service is unsuccessful and the
following error message is in the SQLAgent.out file:
2002-03-18 13:11:46 - ! [298] SQLServer Error: 18456, Login failed for user
'sa'. [SQLSTATE 28000]
2002-03-18 13:11:46 - ! [000] Unable to connect to
server '(local)'; SQLServerAgent cannot start
The following
conditions must be true for the error message to occur:
- SQL Server is installed on a Backup Domain Controller (BDC)
on a computer that is running Microsoft Windows NT 4.0, or on any domain
controller (DC) that is not the first DC in Microsoft Windows 2000 (the
SV_TYPE_DOMAIN_BAKCTRL bit is set in the server role):
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/netmgmt/ntlmapi3_8naq.asp
- The connection properties for the SQLServerAgent service to
connect to SQL Server is set to SQLAuthentication.
WORKAROUND To work around this behavior, you can use either of the
following methods: - Use Windows Authentication for the SQLServerAgent service to connect to SQL
Server.
To use Windows Authentication, follow these steps:
- Open SQL Server Enterprise Manager, expand Server, and then expand Management.
- Right-click SQLServerAgent, and then click to select Properties.
- Move to the Connection tab.
- Click to select the Use Windows Authentication option button.
- Click Apply, and then click OK.
- Start the SQLServerAgent service.
- Start the SQLServerAgent service under a domain account.
STATUSMicrosoft has confirmed that this is a
problem in SQL Server 2000.
| Modification Type: | Major | Last Reviewed: | 10/17/2003 |
|---|
| Keywords: | kbbug kbpending KB320338 |
|---|
|