SQL Service Manager stops automatically after changing the Windows Password
I just found that the computer was running very slowly. I restarted the computer and found that the SQL service manager did not start my database automatically.
The information found on the internet is as follows:
Dear experts, my system is XP and I have installed the SQL Server 2000 Personal Edition.
After installation, you will not be able to log on to "unable to start the service due to login failure", "Error 1069-(unable to start the service due to login failure .), The operation is being performed on the MSSQLServer service"
How can I solve this problem? I have reinstalled it several times.
Thought 1
Change the administrator password to null;
Idea 2:
Change the sqlserver login password to the administrator password. The specific method is to open the Service Manager, find MSSQLServer to open the logon tab under properties, click this account single choice button, Click Browse, find administrator OK, OK. Restart the computer (preferably restart the computer ). OK.
Thought 3:
The administrator password is not changed. We need to create a new system account and use this account the next time we log on, instead of administrator.
Idea 4: (recommended)
Idea 2 is feasible, but what if I change the password next time?
So I thought of creating a separate account for it.
Open Computer Management, create a new user, and add sqlserver to the Administrator group (this is required; otherwise, permissions are insufficient)
Review the logon tab and find sqlserver.
In this way, we will not be unable to start the service due to login failure due to changes to administror.
The above mentioned service is in the following path: My computer -- control panel -- Management Tools -- service -- Right-click MSSQLServer -- properties -- login identity -- select "Local SYSTEM account"
===
for more information, visit www.123de6.cn.
the administrator password has just been changed. Solve the problem. In this Article , Outlook prompts you to enter a password, N accounts, and re-enter n times. It seems that the change to the Windows Password is too wide, and there may be other problems. Now it is not used for the time being, so it will not be met.