1608 error resolution during SQL Server 2008 installation

Always use SQL Server 2000, it is easy to install quickly, do not want to upgrade to 2005/2008. Today, there is a project to use 2008, and then installed under the Windows7, did not expect to encounter a 1608 error, the middle hint a lot of information, the Internet search a bit, Also many encountered this error, tried online methods have not been successful, depressed in search of a foreign method:





 





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








to troubleshooting the issue and please try the following steps:





1. Get the Product Code = ' {aeb9948b-4ff2-47c9-990e-47014492a0fe} '.


2. Byte reverses the "I" and "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.





 





I tried, remove the whole upgradecodes after the smooth installation.





How and when to use SQL Server 2008 log files


Summary.txt


Location:%programfiles%microsoft SQL server100setup bootstraplog





use: This log contains basic information about the issue in a clean, user-friendly log file. This file is displayed when a component's SQL server, operating system environment, specified command-line arguments, specified values, and the overall status of each MSI and MSP file that has been executed are detected.





Troubleshooting: To find errors in this file, you can usually search for errors or failure keywords. For more information about the breakdown, open the listed file in the log that failed at the beginning of the line.








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 also contain previous attempts for this SQL Server Setup program.





Troubleshooting: To find errors in this file, you can usually search for errors or failure keywords. For more information about the breakdown, open the listed file in the log that failed at the beginning of the line.








Detail.txt


Location:%programfiles%microsoft SQL server100setup bootstraplog <yyyymmdd_hhmm>detail.txt</yyyymmdd_hhmm >





Purpose: This log file provides execution details of the log. It is organized at the start of the line with the timestamp of the extension of the generated log. This is one of the most important log files, because it can be used to determine which faults are occurring. Generate logs on a time basis. This means that instead of building their components, the operation is logged here when they are called. This can be used to determine the order in which the process steps are performed, and the operations between the dependencies. This file is generated for a major workflow, such as a workflow that is installed or upgraded.





Troubleshooting: If an error occurs during installation, the end of the error or exception file is logged. To find the error in this file, you must find the end of the file and read it from the bottom to the top to find a record error or an abnormal reverse operation. After you find the line exit feature code to start, it will appear in your Summary.txt file that you can search for errors, Watson, or the exception keyword in the Detail.txt file. The search results next to the exit feature code will help you determine when and for the first time this error occurs.








Detail_componentupdate.txt


Location:%programfiles%microsoft SQL server100setup bootstraplog <yyyymmdd_hhmmss>detail_componentupdate.txt </yyyymmdd_hhmmss>





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





troubleshooting: 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: Use this log file when a failure appears in the Summary.txt file Systemconfigurationcheck section. Typically, you can open and use the systemconfigurationcheck_report.htm file to get all the information you need. However, you are evaluating the rules by searching for additional information about the log: a phrase that failed in this file.








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: www.3ppt.com%programfiles%microsoft SQL server100setup bootstraplog <yyyymmdd_hhmmss> <name>.log </name></yyyymmdd_hhmmss>





Purpose: These log files provide a detailed log of the package installation process. When the specified package is installed, the logs are generated by the Msiexec.exe process. If the installation is successful, you can see a log entry display product: <product name= "" = "" installation= "" completed= "" Successfully "=" "if=" "no=" "errors=" " ></product>





Troubleshooting: The original source of the problem when you use the MSI log file to ensure that you look instead of the passive error message. To perform this action, follow these steps:





the date in the same directory where the sort MSI log has changed.


opens each MSI log file from the log file to each previous log. The return value of 3 or @ Microsoft is not quoted for each log file search. Please note the error message for each file until you find the end of the log without errors. The last log contains the original error. When you look for the first occurrence in the log, you must determine whether the entry is valid because it is not a problem with all return value 3 errors. Some of the requirements of these errors. If you are unsure of the validity of these errors, we recommend that you have one of the Microsoft SQL Server support options available.


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 execution state of the rule. It also provides a brief description of each rule that is executed.





Troubleshooting: You can open the systemconfigurationcheck_report.htm file and Fail keyword lookup and check that any warning entries apply to your environment.