'How do I fix the error:1069 - The service did not start due to logon failure?

I have written my own windows service which interacts with a SQL database and updates it. The service was running fine and seems to be functioning correctly, however of late it seems to go down at random times and cannot restart due to the error designated in the question. I have tried various searches to fix this, but unfortunately I have come up with nothing. The aim is to eventually having this service running on my companies server, but I can't adjust any server settings, I am but a user on the server, so I have restrictions to some settings.

Any quick fixes, would be helpful!

sqlservice


Solution 1:[1]

  1. Open the Services Manager. ( Win + R, then type services.msc )
  2. Then right click on the SQL Server process and click Properties

enter image description here

  1. Then go to Log On, and select This account: enter image description here

  2. Then click Browse, and add your username in the box. (Notice it should contain the domain, in my case is AD\myusername), then Check Names and accept. enter image description here

  3. Finally type your password in the other two fields, and that's it, you should have permission to start your process now.

Cheers!!

Solution 2:[2]

One issue for us was the format of the account user name, we initially used

domain\username

and got the 1069-logon error, then ultimately I tried validating the user name in the properties | logon tab of the Service (in Control Panel / Service Manager), using the "Browse" and "Search" for the user name and it turned it suggested and validated ok with the reverse format

username@domain

This also worked and resolved the 1069 error, and let us script the startup using sc.exe.

Solution 3:[3]

Error 1069 is vague and can have different causes. I am sharing my experience here.

I encountered this error when trying to get a service to run under my account (I am trying to get my services to see the same LocalDB as interactive processes running on my account for development purposes). I use an MSA (Microsoft Account) with Windows’s PIN login normally, so I rarely enter my Windows password. To resolve the issue, I locked my screen, selected Password input instead of PIN input, and then entered my password. I assume this somehow reminded Windows what my password was and made my local account more legit.

Before doing this, you need to configure the user account in question to have the Logon as Service privilege. To do this, open the Group Policy Editor. Expand Computer / Windows Configuration / Security Configuration / Local Policies / User Permissions Assignment and then open Login as Service. From there, you can add your user in question.

Solution 4:[4]

also check for "Deny Logon service" policy. user should not be added over there

Solution 5:[5]

We had this issue as well because the account was set so that the password expired. After we updated the account to not expire and set the password this error stopped.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1
Solution 2 Mosca Pt
Solution 3
Solution 4 varun
Solution 5 campo

Related Questions