SQL Server 2008 installation error 1608 and troubleshooting methods

SQL Server 2008 installation error 1608 and troubleshooting methods

I have been using SQL Server 2000. I don't want to upgrade it to SQL Server 2005/2008 because it is easy and fast to install. today, a project suddenly needs to use 2008, so I installed it in Windows 7. I did not expect to encounter a 1608 error. I found a lot of information in the middle and searched the internet, I have also encountered this error many times. I tried the method on the Internet and failed to find a foreign method:

 

 

SQL Server 2008 Setup fails on Windows 7 Enterprise, Error code 1608

To troubleshooting the issue, please try the following steps tutorial:

1. Get the Product Code = {AEB9948B-4FF2-47C9-990E-47014492A0FE }'.
2. Byte reverses the first part from AEB9948B to B8499BEA.
3. Search in the registry under HKEY_CLASSES_ROOTInstallerUpgradeCodes and find a match.

4. Take a backup of the registry and delete the parent key.
5. Re-run the installation and if it fails again for a different GUID then repeat the steps stated above.

 

I tried to delete the entire UpgradeCodes and successfully installed it.

How and when to use SQL Server 2008 log files
Summary.txt
Location: % ProgramFiles % Microsoft SQL Server100Setup BootstrapLog

Purpose: The log contains basic information about the problem in a clean and user-friendly log file. The component's SQL Server, operating system environment, specified command line parameters, specified values, and overall status of each executed MSI and MSP file are detected.

Troubleshooting: to find errors in this file, you can usually search for errors or failure keywords. For more information about faults, open the listed files in the logs that start with failures.

Summary _ <% ComputerName % _ YYYYMMDD_HHMMSS>. txt
Location: % ProgramFiles % Microsoft SQL Server100Setup BootstrapLog <yyyymmdd_hhmmss> Summary _ <% ComputerName % _ YYYYMMDD_HHMM>. txt </yyyymmdd_hhmmss>

Purpose: This log file contains the same information as the Summary.txt file. In addition, this log may contain previous attempts to install the SQL Server.

Troubleshooting: to find errors in this file, you can usually search for errors or failure keywords. For more information about faults, open the listed files in the logs that start with failures.

Detail.txt
Location: % ProgramFiles % Microsoft SQL Server100Setup BootstrapLog <yyyymmdd_hhmm> Detail.txt </yyyymmdd_hhmm>

Purpose: This log file provides detailed logs for execution. It is organized at the beginning of the line with the timestamp of the log generation extension. This is the most important log file because it can be used to identify faults. Generate logs based on the time. This means that, instead of generating their components, the operation is recorded here when they are called. This can be used to determine the execution sequence of the process steps, the operation execution sequence, and the operation between dependencies. This file is generated for the main workflow, such as the installed or upgraded workflow.

Troubleshooting: if an error occurs during installation, the end of the error or exception file is recorded. To locate an error in this file, you must find the end of the file and read it from the bottom to the top to find an error or abnormal reverse operation. After you find the line exit code to start, it will be displayed in your Summary.txt file. You can search for the error, the exception keyword in the Watson bucket or the Detail.txt file. The search results next to the exit code will help you determine when and when this error occurs for the first time.

Detail_ComponentUpdate.txt
Location: % ProgramFiles % Microsoft SQL Server100Setup BootstrapLog <yyyymmdd_hhmmss> Detail_ComponentUpdate.txt </yyyymmdd_hhmmss>

Purpose: This log file is similar to the Detail.txt file. Generate this file for the component update workflow.

Troubleshooting: the same for Detail.txt.

Detail_GlobalRules.txt
Location: % ProgramFiles % Microsoft SQL Server100Setup BootstrapLog <yyyymmdd_hhmmss> Detail_GlobalRules.txt </yyyymmdd_hhmmss>

Purpose: This log file is similar to the Detail.txt file. This file is generated for global rule execution.

Troubleshooting: This log file is used only when a failure is displayed in the SystemConfigurationCheck section of the Summary.txt file. Generally, you can open and use the SystemConfigurationCheck_Report.htm file to obtain all required information. However, whether you search for other information from the log in the rule for evaluation: the phrase in this file fails.

MSI log file:
<Feature >_< architecture >_< iteration>. log </iteration> </architecture> </feature>
<Feature >_< architecture >_< language >_< iteration>. log </iteration> </language> </architecture> </feature>
<Feature >_< architecture >_< iteration >_< workflow>. log </workflow> </iteration> </architecture> </feature>
Location: % ProgramFiles % Microsoft SQL Server100Setup BootstrapLog <yyyymmdd_hhmmss> <name>. log </name> </yyyymmdd_hhmmss>

Purpose: These log files provide detailed logs of the package installation process. When the specified package is installed, these logs are generated during Msiexec.exe. Whether the installation is successful. You can see a log product: <product name = ""-= "" installation = "" completed = "" successfully "=" "if =" "no =" "errors =" "> </product>

Troubleshooting: when you use an MSI log file, make sure that you read the error message instead of the original source. To perform this operation, follow these steps:

The dates for sorting MSI logs that have been changed in the same directory.
Open each MSI log file from each previous log file. Search for each log file returns 3 or @ Microsoft without quotation marks. There are no errors until you find the end of the log. Please note the error information of each file. The last log contains the original error. When you search for the first match in the log, you must determine whether the entry is valid because not all returned values 3 are incorrect. Requirements for these errors. If you cannot determine the validity of these errors, we recommend that you have one of the available Microsoft SQL Server support options.
SystemConfigurationCheck_Report.htm
Location: % ProgramFiles % Microsoft SQL Server100Setup BootstrapLog <yyyymmdd_hhmmss> SystemConfigurationCheck_Report.htm </yyyymmdd_hhmmss>

Purpose: This file contains a friendly version of the rule execution status. It also provides a brief description of each rule to be executed.

Troubleshooting: you can open the SystemConfigurationCheck_Report.htm file and the failure keyword to find and check whether any warning entries are applied to your environment.