First, we will introduce two commonly used solutions on the Internet:
1. My Computer--Control Panel--Administrative Tools--Service--Right-click MSSQLSERVER--Properties--Login--Login Identity--Select "Local System Account"
or :
2. My Computer--Control Panel--Administrative Tools--Service--right-click MSSQLSERVER--Properties--Login--Login Identity--Select "This Account"--Enter your modified password and confirmation password administrator password.
The difference between the two:
choose the first method, and if you change the administrator password in the future, you don’t need to adjust it (but the person who logs in to the operating system is the system administrator).
Choose the second method, and if you change the administrator password in the future, you don’t need to adjust it again. Repeat the above operations.
The following is a situation I encountered:
This morning, my colleague told me that his SQL could not log into his "Enterprise Manager", and the error reported was "Error 1069, the service cannot be started due to login failure." I checked online. I have reached the above two solutions, but when I saw the service window, I found another place that may cause this problem, as shown below:
We first find the MSSQLSERVER service, and then check its properties.
I found that a domain account was used for verification when starting the service, so I asked if the password for the login domain had been changed. The answer was yes, because the domain has been set up to require the user to change the password after a certain period of time, and it cannot be the same as the previous password. (Except for the empty password, I have done experiments on this ^_^). So I reset the password here, restarted the service successfully, and SQL can also log in successfully.
Through this problem, we found that when the domain password is modified, the login verification information used by the corresponding service will not be automatically updated and needs to be updated manually to solve this problem. If you find it troublesome, it is easier to directly change the login identity to "Local System Account" like the solution above.