How can I resolve the error 'An error 1069 - (The service did not start due to a logon failure)' for SQL Server?

A. SQL Server is just like any other NT service in that it can be defined to run using the credentials of an NT user account. It can also run under localsystem account, but if you are getting this error then you must have defined a user account.

Related: Automate detection of Logon failure in a domain environment 

Go to control panel/services. Choose the mssqlserver service (or SQLExecutive/SQLAgent if they are failing) and then choose startup. Check what NT account is being used. Make sure that the password is correct and check with NT user manager that the account has not been deleted or expired.

If the account details seem ok, then check that it has "logon as a service" user right (again with user manager).

If this doesn't resolve the issue then try logging on locally to the NT box with the same NT account and see what error(s) you get.

Related: Logon failures on BDC due to secure channel problem


Discuss this Article 17

Anonymous User (not verified)
on May 20, 2005
Este articulo resolviò mi problema! Gracias!!!
Anonymous User (not verified)
on Aug 5, 2005
fantastic, if i meet you in a pub, I'll buy you a beer mate!
Anonymous User (not verified)
on Aug 16, 2005
THANKS
Erik (not verified)
on Jul 3, 2001
Thank you! It solved my problem. Thanks again!
Name (required):Eric (not verified)
on Jun 24, 2004
Your Comments (required):Solved my problem as well.
Vinayak (not verified)
on Jun 30, 2005
Hey buddy this works well for me thanx!
josepbocanegra (not verified)
on May 24, 2006
Very useful. You have solved my problem
Anonymous User (not verified)
on May 2, 2005
Thanks, worked for me!
Anonymous User (not verified)
on Jul 3, 2005
it worked thanx

Please or Register to post comments.

Upcoming Training

Mastering System Center 2012

During over 6 hours of training you can join John Savill from your computer as he will walk you through the key components and capabilities of System Center 2012, what’s involved in using the components, and the benefit they can bring to your environment.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.