About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Error 1069 means the Service Control Manager could not sign the service in with the account it is configured to run as. Windows lists it as ERROR_SERVICE_LOGON_FAILED, 1069 (0x42D): "The service did not start due to a logon failure." After a password change, the first question is whether the service still holds the old password; the System event log says which of several causes you have.
Microsoft's detailed page is written for SQL Server and SQL Server Agent, and it gives no statement about other services. Treat its steps as the source for SQL Server and as a guide, not a rule, for other services. Read the event first, test the account's credentials, and change the service's password only when the test shows what is wrong.
What the error means
Microsoft's page "Error 1069 occurs when you start SQL Server Service" says the error "occurs when the SQL Server or SQL Server Agent service can't sign in by using its configured service account" and lists the causes as "a missing "Log on as a service" right, a disabled or locked account, an expired or incorrect password, and a domain that isn't reachable during startup." You see it in the Services snap-in as "Windows could not start the SQL Server service on Local Computer. Error 1069: The service did not start due to a logon failure." At a command prompt the form is "System error 1069 has occurred. The service did not start due to a logon failure."
The System event log carries the detail. Microsoft says: "Use the event ID and error text in the System event log to select the resolution":
| Event ID | Error text in the event | Meaning |
|---|---|---|
| 7041 | Logon failure: the user has not been granted the requested logon type at this computer. | The account lacks "Log on as a service" |
| 7038 | This user can't sign in because this account is currently disabled. | Account disabled |
| 7038 | The user's password must be changed before signing in. | Password change required at next logon |
| 7038 | The user name or password is incorrect. | Wrong password, or a gMSA flag |
| 7038 | The referenced account is currently locked out and may not be logged on to. | Account locked out |
| 7038 | The specified domain either does not exist or could not be contacted. | Domain not reachable at start |
Microsoft's page on changing the passwords of SQL Server service accounts adds that the SQL Server Configuration Manager "is the tool designed and authorized to change the settings of the SQL Server services", and that changing a SQL Server service through services.msc "doesn't always change all of the necessary settings and might prevent the service from functioning properly."
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Service still holds the old password | Event 7038, "The user name or password is incorrect." | runas with the account and its current password succeeds, while the service still fails |
| Password reset has not been applied to the service, or the new password is mistyped | Same event | runas with the new password fails |
| Account must change its password at next logon | Event 7038, "The user's password must be changed before signing in." | The account's properties show the option set |
| Account disabled or locked out | Event 7038, disabled or locked text | The account's properties show disabled or locked |
| "Log on as a service" missing or a Deny right applies | Event 7041 | Local Security Policy shows the account missing from the right, or present under the Deny right |
| Domain cannot be contacted at start | Event 7038, domain text | The failure only happens at boot, or while the domain is unreachable |
Prove the cause before changing anything
Steps 1, 3 and 4 only read. Step 2 does not, so it carries its own warning.
Risk: step 2 signs in as the service account. A wrong password counts as a failed sign-in and can lock the account, which stops every other service and task that uses it. Check your lockout policy first or ask the domain administrator.
- In Event Viewer, open the System log and find the Service Control Manager event for the service. Note the event ID and the error text.
- If the text is "The user name or password is incorrect.", test the credentials with Microsoft's
runascheck. Replace the placeholders with the machine or domain name and the service account, then type the password when asked:
runas /user:<localmachine>\<SQLServiceAccount> cmd
Microsoft says: "If the command succeeds, carefully type the same credentials" into the service; "If the command fails and reports the same issue, reset the password for the Windows sign-in."
- For the other 7038 texts, check the account itself. For a local account, open Computer Management (compmgmt.msc) and look at the user under Local Users and Groups. For a domain account, open Active Directory Users and Computers and look at the Account tab.
- For event 7041, open Local Security Policy (secpol.msc), expand Local Policies, select User Rights Assignment, and check "Log on as a service" and, under the Deny rights, "Deny log on as a service".
Example (illustrative): at contoso.com.au the password for CONTOSO\svc-sql was rotated on Monday. On sql01 the instance MSSQL$SQLPROD now fails with Error 1069. The System log shows event 7038, "The user name or password is incorrect." Running runas /user:CONTOSO\svc-sql cmd with the new password opens a command window, so the account and password are good and the service is holding the old one.
Fix
Use the row of the event table that matches your event. All the steps below are Microsoft's, for SQL Server.
Wrong or outdated password (event 7038, "The user name or password is incorrect.")
Before you change it, write down the service name and the account name shown for it, so you can confirm you are editing the right service.
Risk: the next steps change the password a service signs in with. If the password is typed wrongly, the service stays down. Restarting the SQL Server service afterwards interrupts anything connected to it.
If the runas test succeeded, Microsoft says to type the same credentials in SQL Server Configuration Manager: select SQL Server Services, right-click the SQL Server service, select Properties, and on the Log On tab type the password in the Password and Confirm Password boxes, then select OK. Microsoft's password page says that change "takes effect immediately, without the need to restart the SQL Server service". Microsoft's 1069 page then says to restart the SQL Server service.
To undo it: there is no way back worth taking. The earlier password is the one that failed. If you also changed the account name, put the name you wrote down back on the same Log On tab.
If the runas test failed and reported the same issue, Microsoft says the password for the Windows sign-in is the fault and has to be reset.
Before you reset it, write down the account name and list everything else that signs in with it: other services, scheduled tasks and applications.
Risk: resetting the account's password changes the sign-in for every other service, scheduled task and application that uses the same account, and they fail until each one is updated. Reset it only for an account that you have confirmed is the service's own. Restarting the SQL Server service interrupts anything connected to it.
Microsoft's steps: for a local account, open Computer Management (compmgmt.msc) and reset the password of the local user; for a domain account, open Active Directory Users and Computers and update the password under Users. Then enter the same credentials in SQL Server Configuration Manager, as above, and restart the SQL Server service.
To undo it: set another password and update every place that uses the account, because the old password is replaced and cannot be restored.
"Log on as a service" missing (event 7041)
Before you change it, record who holds the "Log on as a service" right and the "Deny log on as a service" right on the server, from the Local Security Policy console.
Risk: the next steps change the user rights on the server. A Group Policy object can remove the right again, and a wrong grant gives the account the right to run services on this server. Microsoft says: "check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right."
Microsoft's steps: start the Local Security Policy snap-in (secpol.msc), expand Local Policies, select User Rights Assignment, and assign "Log on as a service" to the service account. Microsoft also says to check whether the account has any Deny user right: "Remove any Deny user rights from the SQL Server service account and then retest", for example revoking SeDenyServiceLogonRight when both it and SeServiceLogonRight are assigned.
To undo it: open the same policy and remove the account from the right you added, or add it back to the Deny right if you removed it, as your record shows.
Disabled, password change required, or locked out (event 7038)
Before you change it, note the state of the account: whether it is disabled, whether "User must change password at next logon" is ticked, and whether it is locked.
Risk: enabling an account, clearing the password-change requirement, unlocking an account or setting a new password for it changes who can sign in with it, and a new password changes the sign-in for every other service, scheduled task and application that uses the account. Someone may have disabled or locked it on purpose. Restarting the service interrupts anything connected to it.
Microsoft's steps: enable the account (Local Users and Groups for a local account, Active Directory Users and Computers for a domain account), clear "User must change password at next logon" or sign in interactively to a client machine and set a new password, or select "Unlock account" on the Account tab and set a strong password. Then restart the service and, if the password changed, update it in SQL Server Configuration Manager.
To undo it for a disabled account or the password-change flag, set the option back as you noted it. There is no way back from unlocking a locked account, or from setting a new password, because a lockout is a state and not a setting and the old password is replaced.
The domain cannot be contacted at start (event 7038)
Microsoft's page offers delayed start for the SQL Server service, a service recovery action of restarting it, or a dependency on the Netlogon service set with sc config. It warns that the restart option "isn't recommended for SQL Failover Cluster Instances (FCIs) or Availability Groups (AGs)". Microsoft's page does not say whether the sc config form keeps existing dependencies, and shows no command that reads them. The other two options change the service's start type or recovery settings, and Microsoft's page gives no steps for them, so plan them separately.
Confirm the fix
- Start the service and see that it reaches Running without the 1069 message.
- Check that the System log shows no new 7038 or 7041 for the service.
Disruptive step: restarting the server interrupts everyone using it, so do it in a maintenance window.
- Restart the server once and confirm the service starts on its own.
What to watch afterwards
- The next password change. A service that runs under a changed password fails the same way again; set the account's password policy and the update steps together.
- Other services and tasks using the same account. Microsoft's page does not list them.
- If you use group managed service accounts, Microsoft's page notes the
IsManagedAccountflag as a separate cause of event 7038 for gMSA-run SQL Server services.
Read next
Related articles you may want next.
- Troubleshooting"Error 1053: The service did not respond to the start or control request in a timely fashion"Windows error 1053: service did not respond in a timely fashion. Prove the cause, then raise ServicesPipeTimeout carefully with a way back.Read article
- Backup & RecoveryGroup managed service accounts after a restore: the key that makes every passwordPlan gMSA recovery with protected directory backups, KDS keys, authorised hosts and service dependencies after deletion or credential exposure.Read article
- TroubleshootingAccount Keeps Locking Out: Find the Source From Event 4740 to the ProcessAccount keeps locking out? Read event 4740 on the PDC emulator, follow 4771, 4776 and 4625 to the source computer, then find the stale credential there.Read article
Risks and limits
These commands have not been run or lab-tested.
Microsoft's detailed steps are for SQL Server and SQL Server Agent; its pages give no steps for other services and no statement that other services behave the same way. Event IDs 7038 and 7041 and their texts are quoted from that page. Microsoft's pages do not describe how to change another service's password.
Sources
- System Error Codes (1000-1299) — Microsoft Learn, page dated 2025-07-14, accessed 22 November 2026
- Error 1069 occurs when you start SQL Server Service — Microsoft Learn, page dated 2026-10-16, accessed 22 November 2026
- SQL Server Configuration Manager: Change the password of the accounts used — Microsoft Learn, page dated 2026-03-18, accessed 22 November 2026
This article was originally published on .