none
The service did not start due to a logon failure

    Question

  • Hi all,

    I'm having some severe problems with the sql server service account on a cloned VM. When I try to change the service account through sql server configuration manager I get the following error message:

    Here is some background info:

    • this is a VM, Win 2008 R2 Std
    • the VM was recently cloned 
    • A clean SQL Server 2008 was upgraded to R2 *before* the clone process
    • The machine is in an AD domain, the account is a new, empty domain account
    • The sql server service is able to start with the Local System and the AD service account that was used before the cloning...
    • ...no other accounts work, not even a domain admin account

    I was able to find this article but it refers to a domain controller and the services are not the same:
    http://support.microsoft.com/kb/955496 


    Lumbago
    www.thefirstsql.com
    • Edited by Lumbago Monday, March 28, 2011 6:42 AM pic didn't work
    Monday, March 28, 2011 6:41 AM

Answers

  • The root cause was discovered after a week or so after talking to one of the AD-guys and it was all caused but the fact that the service account needed to have "log on as a service" permissions set in a central policy in AD. The sql server configuration manager wasn't able to override this policy but services.msc obviously was so it was all very confusing.
    Lumbago
    www.thefirstsql.com
    • Marked as answer by Lumbago Thursday, April 07, 2011 8:28 AM
    Thursday, April 07, 2011 8:27 AM

All replies

  • http://support.microsoft.com/kb/955496
    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/
    Monday, March 28, 2011 6:50 AM
  • This is exactly the same link as in my original post, and we tried both workarounds to no avail.
    Lumbago
    www.thefirstsql.com
    Monday, March 28, 2011 6:54 AM
  • Can we have more details about the failure:

    1. SQL Server error logs.
    2. When there is a failure in the SQL Server service to start, do we see any errors in the Application/System Event logs? If yes, can you provide the same.

    Thanks


    Chaitanya (http://twitter.com/chmediko)
    Monday, March 28, 2011 9:43 AM
    1. There are no messages in the sql server logs, other than the messages that normally appears when the service is shut down
    2. The message in the Windows System log is: This service account does not have the required user right "Log on as a service." I did however add this permission  manually in the Local Security Policy but it doesn't help. I did this prior to posting here... 

    Lumbago
    www.thefirstsql.com
    Monday, March 28, 2011 10:16 AM
  • I was able to find a blog post that describes the exact problem I'm having except for the fact that mine is a freshly installed server instead of an old one

    -> http://computersplace.net/microsoft-releated/windows-server-howto/sql-server-unable-log-domainserviceaccount.html

    And the workaround is the same as what we found after a GOOD while of debugging; to set the account using services.msc instead of sql server configuration manager. I would like to know why this happens though so if anyone has any insights I'm all ears...


    Lumbago
    www.thefirstsql.com
    • Proposed as answer by Peja Tao Thursday, April 07, 2011 8:19 AM
    • Unproposed as answer by Lumbago Thursday, April 07, 2011 8:28 AM
    Tuesday, March 29, 2011 7:12 AM
  • I was just about to ask you to try from services console.

    For me it seems like the configuration manager is not working properly due to some WMI issues. You might need to fix the WMI issues before you can use configuration manager properly.


    Regards, Ashwin Menon My Blog -> sqllearnings.wordpress.com
    Tuesday, March 29, 2011 7:18 AM
  • The root cause was discovered after a week or so after talking to one of the AD-guys and it was all caused but the fact that the service account needed to have "log on as a service" permissions set in a central policy in AD. The sql server configuration manager wasn't able to override this policy but services.msc obviously was so it was all very confusing.
    Lumbago
    www.thefirstsql.com
    • Marked as answer by Lumbago Thursday, April 07, 2011 8:28 AM
    Thursday, April 07, 2011 8:27 AM
  • @Lumbago, did you know exactly what the AD guys did? I'm having the same problems. Thanks.
    Saji Ijiyemi
    Wednesday, April 13, 2011 3:14 PM