Failed to Install SQL SERVER 2000. You no longer need to reinstall the system!

My colleague's machine encountered the following prompt when installing SQL SERVER 2000:
"A previous program has been installed to create a pending file on the installation computer. You must restart the installer before running it ".
In the past, I often chose to reinstall the system to solve this problem. Sometimes it is a waste of time to install the system even if you have been searching for a long time. Therefore, the fastest way is to reinstall the system. My own machine has never encountered this problem, because I have to use SQL server, so I will install the system after installing the driver, so there is no problem. It seems that this is still a problem of SQL SERVER software compatibility.
However, the current problem is that there are more and more software installations, and it is too time-consuming to reinstall the system. It is better to find a solution.
So I found the solution to this problem:
Open the Registry Editor, find the PendingFileRenameOperations project in HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager, and delete it. In this way, you can clear the temporary installation project.
Of course, this method is not only applicable to the installation of SQL SERVER, but also to the installation of other software.

However, the problem persists. Then there were the following problems:
　　"Command line option syntax error. Type command /? For help ".
Next, find the cause. Some people think that MDAC should be re-installed, but I remember that MDAC should be installed before SQL SERVER is installed. Others also say that the registry should be modified: find HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ setup and delete ExceptionComponents, But I didn't try this.
I copied my software installer from "D: \ Application Software \ PersonalSQL" to "D: \ PersonalSQL". This prompt is not displayed when I run the installation again.

But the problem persists. After the installation, the following problems occur:
"The installation program fails to configure the server. For more information, see Server Error log and c: \ windows \ sqlstp. log ".
I am suffering from this.
The following information is displayed when you view the log:

1 ####################################### ########################################
2
3 is starting?
4Chinese_PRC_CI_AS
5-m-Q-T4022-T3659
6 is working with the service?
7 driver = {SQL server}; server = LIB; UID = sa; PWD =; database = master
8 [Microsoft] [ODBC driver manager] No data source found
9 driver = {SQL server}; server = LIB; UID = sa; PWD =; database = master
10 [Microsoft] [ODBC driver manager] No data source found
11 driver = {SQL server}; server = LIB; UID = sa; PWD =; database = master
12 [Microsoft] [ODBC driver manager] No data source found
13SQL Server configuration?
14 ####################################### ########################################
15
1614: 00: 08 Process Exit Code: (-1)
1714: 00: 13 the installer fails to configure the server. For more information, see Server Error log and C: \ WINDOWS \ sqlstp. log.

To solve this problem, I executed the following command in the command line:

1odbcconf.exe/S/Lv odbcconf. log/F % systemroot % \ system32 \ mdaccore. rsp
2odbcconf.exe/S/Lv odbcconf. log/F % systemroot % \ system32 \ sqlclnt. rsp
3odbcconf.exe/S/Lv odbcconf. log/F % systemroot % \ system32 \ odbcconf. rsp
4odbcconf.exe/S/Lv odbcconf. log/F % systemroot % \ system32 \ redist. rsp

For the sake of insurance, "advanced options" are selected during installation, and "rebuild Registry" is selected in the next step ". The installation is successful!

At that time, I was very happy to start the SQL SERVER service and open the Enterprise Manager. Another problem occurred!Console unavailable!I had to reinstall the component again, but this time I chose "advanced options" and then added and deleted the component to select all the components. Re-install. It will soon end. Go to the Enterprise Manager again and now you will see the service.
However, the system still prompts that the connection fails. Edit the registration attribute, change the authentication method to the Windows/SQL hybrid mode, and change the sa password to null.
Finally succeeded!