The main reason why SQL Server cannot be started on the login, here's a little trick to solve SQL Server's inability to start, and if you've had problems with SQL Server that can't be started, take a look.
SQL Server sometimes fails to start correctly because the Executive service cannot log on. One of the main reasons is that LocalSystemAccount and Administratorgroup cannot fully control two registry keys.
1 Open the Start menu and choose Run. Click the browse button to start browsing until you find the root directory of Windows2000 (usually Winnt). Enter the system directory and locate the Regedt32.exe and select it into the dialog box
and click the OK button. Registry Editor launches, displaying all hive units in different cascade child windows
In
2 Select Window menu item HKEY_LOCAL_MACHINE, its child window display. Maximize the window for ease of use.
3 Use the tree control on the left window to navigate to the Software\microsoft\mssqlserver\sqlexecutive subkey. Click the subkey to select it and display its value in the right window.
Navigates to the System\currentcontrolset\services\sqlexecutive subkey. Click the subkey to select it and display its value in the right window. Ensure that LocalSystemAccount and Administratorgroup have full control over the item and its subkeys. Repeat the above check for the System\currentcontrolset\services\mssqlserver\sqlexecutive subkey.
SQL Server has several levels of task failures, including partial task execution failures and all task execution failures. In the latter case, a recurring problem occurs when a registry entry conflicts with the use of a named pipe.
Navigates to the Software\microsoft\mssqlserver\sqlexecutive subkey. Click the subkey to select it and display its value in the right window. Navigate to the entry for the value ServerHost. Use the String Editor to change its value so that it does not include the server name (only the well-known pipe you want to use).
The above is the SQL Server can not start processing methods, I hope to help you learn.