1. Delete the SQL installation directory under Program files (back up important data first)
C: \ Program Files \ Microsoft SQL Server \ 80 \ Tools.
C: \ Program Files \ Microsoft SQL Server \ MSSQL.
2. Delete ExceptionComponents: HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ setup
Delete "MSSQLServer": HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSSQLServer.
3. Delete "MSDTC": HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ MSDTC.
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 (this project will be automatically generated, and the startup time will be generated by yourself .)
I have tried the above method more than 20 times, and each time it is successful. I installed SQL2000 eight times on my machine (2003) one afternoon. I installed it and uninstalled it again, and performed eight times in total, yesterday, I also succeeded on my friend's xp machine.
There may be a lot of content in this project, and this method can be used only when the above methods are not feasible (Be sure not to delete all)
Before deleting the content, read the description.
4. The Sqlstp. log file in the Windows directory, which lists detailed information about the operations performed by the installer and contains all errors encountered during installation. By checking this file, you can learn in detail where the installation fails and why it fails.
5. The error message during SQL installation is stored in a Log file named Errorlog. By default, this file is stored in the Program Files \ Microsoft SQL Server \ Mssql \ Log directory. This error log contains the errors that SQL Server encounters when the installer tries to start SQL Server. This information can help you thoroughly check the cause of the error.
6. Another component to be checked is the Microsoft Data Access Component (MDAC) Installer, Which is started as part of the SQL Server 2000 installer. The SQL Server 2000 installer installs MDAC 2.6. The MDAC installer creates a separate log file named Dasetup. log. You can view this log file and ensure that the MDAC installer has no problems.