SQLServer2000 startup 1069 error Solution

First, we will introduce two common solutions on the Network: 1. my computer -- control panel -- Administrative Tools -- service -- Right-click MSSQLSERVER -- properties -- login identity -- Select Local SYSTEM account or: 2. my computer -- control panel -- Administrative Tools -- service -- Right-click MSSQLSERVER -- properties -- login identity -- select this account -- password and Confirm Password

First, we will introduce two common solutions on the Network: 1. my computer -- control panel -- Administrative Tools -- service -- Right-click MSSQLSERVER -- properties -- login identity -- Select Local SYSTEM account or: 2. my computer -- control panel -- Administrative Tools -- service -- Right-click MSSQLSERVER -- properties -- login identity -- select this account -- password and Confirm Password

First, we will introduce two common solutions on the network:

1. My computer -- control panel -- Management Tools -- service -- Right-click MSSQLSERVER -- properties -- login identity -- select "Local SYSTEM account"

Or:

2. my computer -- control panel -- Administrative Tools -- service -- Right-click MSSQLSERVER -- properties -- login identity -- select "this account" -- enter your modified administrator password in the password and Confirm Password.

Differences between the two:

Select the first method. The administrator password will be changed later. You do not need to adjust the password (but the system administrator is required to log on to the operating system)

Select the second method, modify the administrator password later, and repeat the above operation.

Below is a situation I have encountered:

This morning, my colleague told me that his SQL statement could not be logged on to his "Enterprise Manager". The error "1069 error, unable to start the service due to logon Failure" was reported ", I found the above two solutions on the Internet, but when I saw the service window and found another cause of this problem, we first found the MSSQLSERVER service and then checked its properties, the domain account was used for verification when the service was started, so I asked if I had modified the login domain password. The answer was changed because the domain was set, after a certain period of time, the user is required to change the password, and cannot be the same as the previous password (except for the blank password, this is my tutorial ^_^ ). Therefore, you can reset the password and restart the service. You can also log on to SQL.

After the domain password is changed, the login verification information used by the corresponding service is not automatically updated and needs to be updated manually. If you are too troublesome, it is easier to change your login identity to a "Local SYSTEM account" just like the solution above.