SQL Server service does not start successfully because of a logon failure

Article translations Article translations
Article ID: 282254 - View products that this article applies to.
This article was previously published under Q282254
Expand all | Collapse all

SYMPTOMS

When you restart Microsoft SQL Server or SQL Server Agent, the service may fail to start with the following error message:
Error 1069: The service did not start due to a logon failure.

CAUSE

This problem occurs because the password for the SQL Server startup service account or the SQL Server Agent startup service account is not correct. This problem can occur when the password for the account is changed but the password information was not updated for the SQL Server service or the SQL Server Agent service.

WORKAROUND

To solve this problem, type the correct password in the Microsoft SQL Server service account on the SQL Server host computer.

To correct the password in Microsoft Windows 2000 Server and Microsoft Windows XP:
  1. Click Start, point to Settings, and then click Control Panel.
  2. Double-click Administrative Tools, and then double-click Services.
  3. Use one of the following steps based on your instance type:
    • For a default instance of SQL Server, double-click MSSQLServer, and then click the Log On tab.
    • For a named instance of SQL Server, double-click MSSQL$YourInstanceName, and then click the Log On tab. Replace YourInstanceName with the actual name of the SQL Server instance.
    • For a default instance of SQL Server Agent, double-click SQLAgent, and then click the Log On tab.
    • For a named instance of SQL Server Agent, double-click SQLAgent$YourInstanceName, and then click the Log On tab. Replace YourInstanceName with the actual name of the SQL Server instance.
  4. Type the correct password in the Password and Confirm password textbox, and then click OK.
To correct the password in Microsoft Windows NT 4.0:
  1. Click Start, point to Settings, and then click Control Panel.
  2. Use one of the following steps based on your instance type:
    • For a default instance of SQL Server, double-click MSSQLServer, and then click the Log On tab.
    • For a named instance of SQL Server, double-click MSSQL$YourInstanceName, and then click the Log On tab. Replace YourInstanceName with the actual name of the SQL Server instance.
    • For a default instance of SQL Server Agent, double-click SQLAgent, and then click the Log On tab.
    • For a named instance of SQL Server Agent, double-click SQLAgent$YourInstanceName, and then click the Log On tab. Replace YourInstanceName with the actual name of the SQL Server instance.
  3. Type the correct password in the Password and Confirm password textbox, and then click OK.
NOTE: Changing the password through the Services applet allows SQL Server to start successfully; however, if Microsoft Search (Full-Text Service) is installed, it requires a subsequent password change through SQL Enterprise Manager (SEM).

Note If you are using SQL Server 2005, see the "Changing passwords and user accounts" topic in SQL Server 2005 Books Online.

The following section is from SQL Server 2000 Books Online:
"After changing the SQL Server service account information in Control Panel, you must also change the SQL Server service account in SQL Server Enterprise Manager. This allows the service account information for Microsoft Search service to remain synchronized as well.

Important: Although the Microsoft Search service is always assigned to the local system account, the full-text search engine tracks the SQL Server service account in Windows. Full-text search and failover clustering are not available if Windows password changes are not reset using SQL Server Enterprise Manager."
Using SEM, right-click the Server, click Properties, and then click the Security tab. Under Startup service account, enter the appropriate account and password.

MORE INFORMATION

If you are using Kerberos Security Support Provider Interface (SSPI) authentication in a SQL Server 2000 and Microsoft Windows 2000 environment, you must drop your old service principal name (SPN), and then create a new one with the new account information. See the "Security Account Delegation" topic in SQL Server 2000 Books Online for details about using SETSPN to do this.

Properties

Article ID: 282254 - Last Review: February 22, 2007 - Revision: 8.3
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Express Edition
  • Microsoft SQL Server 2005 Workgroup Edition
Keywords: 
kbprb KB282254

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com