Logon failure: the user has not been granted the requested logon type at this computer.error for SQL Services even though account has Log on as a Service priveledges

  • I have a 2008 R2 instance running on a Windows 2008 Virtual Machine.  After a server reboot I lost the ability to start services with the existing user account (I've actually tried 3 different user accounts..)  I verified that the accounts have Log on as a Service and Log on as Batch Job privileges and the correct passwords are being used.  The account that I have been using is also a sys admin and is working on another 2008 R2 instance on another VM. I can start services under a Local System Account but when I try otherwise I get an Error 1069:  The service did not start due to a logon failure.  My System Event log shows the failure as well.  I'm at a loss at where else to look since most solutions point to password changes and account access.  Any advice would be very much appreciated.

  • How do you set the service account? You should use the SQL Server Configuration Manager, since this also grants the permissions needed.

    [font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]

  • Thanks for the reply.  I have tried changing both through the Configuration Manager and in Services.

  • Could there be any DENY in the AD?

    [font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]

  • I've assumed that, since the user account is working on another SQL instance that there would not be any deny.  Any recommendation on how I could confirm this would be appreciated.

  • craig.d.brown - Tuesday, March 13, 2018 11:00 AM

    I've assumed that, since the user account is working on another SQL instance that there would not be any deny.  Any recommendation on how I could confirm this would be appreciated.

    You'd have to get in touch with whoever is the Active Directory administrators to find out.  There is an option to restrict the times and / or the computers an account can log in during / too.  Possibly the AD Admins set this for your service account, such that it can only log in to one server (the working one,) rather than any server / computer.

  • Thanks for the continued replies.  I have actually tried to accounts that are not in use anywhere else, as well as ones that are in use on other servers, and it didn't solve the problem.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply