Reasons and solutions for server startup failure after installing SQL2005 or server startup failure after installation

To commemorate, my first blog in the community, after two days of countless repeated answers and failed attempts, finally found a solution, I hope it can help others, and at the same time express the useless answers to various communities indignation. For the specific installation process, please refer to the tutorial of Mr. Hao Bin. Click to open the link

Below I share my failures:

Error during installation:

1. IIS and ASP warnings appear when installing SQL .

It is because IIS and Framework are not installed , you can download it directly from Baidu, after installation, click to enable or disable Windows functions in the control panel, programs and features,


Check the two boxes below, check all of them, and check the boxes that are displayed in the front, click to open the lower-level files, and make sure all of them are checked so that no warning will appear


2. When writing to the registry, OpenWithList cannot be opened .

After testing, it has nothing to do with SQL. It is the system that prevents the user from forcibly closing this item by misoperation. Just ignore it.

3. When the control is installed later, the SQL service will fail to start .

I have done experiments on WIN7 and WIN10, this situation will not occur on WIN7, guess is that the file is lost due to the incompatibility between WIN10 and 05, in short, if this happens, first find the following file (usually in the C drive by default) , according to your own installation SQL path), to be on the safe side, you can copy one and put it in another folder for backup (I didn’t make a backup because I tested it, and I don’t need this file later)


Then download the two files in the link, unzip and copy them to this folder, remind whether to replace them, replace them all directly, and then click Retry in the SQL installer. Click to open the link


So far, the problems I encountered during the installation process have been solved. The following is the problem encountered when starting SQL:

1. There is no server name when opening SQL for the first time .

The server name is the computer name\instance name , or (local) . The computer name is viewed in My Computer-Properties. The instance name is the instance name from the installation. For example, the computer name is 123, the instance name is SQLServer2005, and the server name is 123\ SQL Server 2005.

2. After entering the server name, the service fails to start .

Right-click My Computer, manage, find services, find SQLServer2005 on the right, right-click to enable,

If it fails, find the option below, disable all three on the right, and then enable the service.


3. The user name or password is wrong.

On the login interface, choose Windows login directly. If you choose the following, you must enter the password you entered during installation.


If it doesn’t work, go to My Computer-right-click Management-Service-SQLServer-right-click Properties-login, and select the local system account.



The above problems are all problems I encountered during installation and use. Personally, the biggest problem is the third step in the installation process.

There are answers to this step on the Internet, but other steps have been performed (restore the backup file, download the SP4 patch package, etc.).

I installed SQL once on WIN7, but there was no problem that the service could not be started, so I boldly inferred that the problem was on the WIN10 system. Sure enough, after I only replaced but did not restore and downloaded the update package, the following problems did not reappear , but sometimes the SQL Server in the service still needs to be started manually (once the SQL login fails, the server error prompt is mostly because it is not enabled in the service), but this is not worth mentioning. This concludes this post.



Guess you like

Origin blog.csdn.net/qq_41749924/article/details/79610160