By: Matteo Lorini | Comments (2) | Related: > Upgrades and Migrations
Problem
I have a production SQL Server with multiple instances. We are working through the SQL Server 2005 Service Pack 3 installation. Unfortunately, we have run into Error: 29565 SQL Server Setup cannot upgrade the specified instance because the previous upgrade did not complete. Where can I find out which SQL Server instance had the issue and the resolution? Do I need to reinstall SQL Server or do I have another option?
Solution
Not long ago, I had to install SQL Server 2005 Service Pack 3 on a multi instance SQL Server. The issue was that SP3 wizard was able to upgrade all the installed services like Reporting, Analysis, and the SQL Server Name Instance but; it failed to upgrade the Default SQL Server Instances. By looking to the summary.txt file I was able to see the following:
Time: 07/26/2009 03:48:06.568
KB Number: KB955706
Machine: ATLANTA
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 3
Package Version: 4035
Command-line parameters specified:
Cluster Installation: No
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.00.1399.06 x86
Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 ENTERPRISE
Analysis Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 ENTERPRISE
Reporting Services (MSSQLSERVER) ENU RTM 9.00.1399.00 x86 ENTERPRISE
Database Services (SQL2005) ENU RTM 2005.090.1399.00 x86 ENTERPRISE
Analysis Services (SQL2005) ENU RTM 2005.090.1399.00 x86 ENTERPRISE Notification Services ENU RTM 9.00.1399.00 x86 ENTERPRISE
Integration Services ENU RTM 9.00.1399.00 x86 ENTERPRISE
SQL Server Native Client ENU 9.00.1399.06 x86 Client Components ENU RTM 9.00.1399.06 x86 ENTERPRISE
MSXML 6.0 Parser ENU 6.20.1099.0 x86
SQLXML4 ENU 9.00.1399.06 x86
Backward Compatibility ENU 8.05.1054 x86
Microsoft SQL Server VSS Writer ENU 9.00.1399.06 x86
**********************************************************************************
Products Disqualified & Reason
Product Reason
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
SQLWriter Microsoft SQL Server VSS Writer Service NT AUTHORITY\SYSTEM 2672
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 1399
Product Version (Final) : 4035
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log
Error Number : 0
Error Description : ----------------------------------------------------------------------------------
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
Error Number : 29565
Error Description : MSP Error: 29565 SQL Server Setup cannot upgrade the specified instance because the previous upgrade did not complete. Start the Remote Registry service and go to Add/Remove Programs, select the Change button for Microsoft SQL Server 2005, and then select SQL instance MSSQLSERVER and complete the setup.
----------------------------------------------------------------------------------
Product : Analysis Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) : 4035
Status : Reboot Required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB955706_sqlrun_as.msp.log
Error Number : 3010
Error Description :
----------------------------------------------------------------------------------
Product : Database Services (SQL2005)
Product Version (Previous): 1399
Product Version (Final) : 4035
Status : Reboot Required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
Error Number : 3010
Error Description :
----------------------------------------------------------------------------------
The point is that the service pack 3 upgrade to the Database Services (MSSQLSERVER) instance could not continue because a previous attempt to patch or upgrade SQL Server failed. The recommended way to fix this problem was to install SQL Server from scratch. In my situation; it was not possible because the server was miles away locked in a secure environment, of which, I had not physical access. After consulting with Microsoft Support, we were able to find a workaround solution to the problem. The main idea was to modify a registry value in order to let the installation of service pack go through smoothly.
This is what we did:
- We ran regedit and drilled to: HKLM\Software\Microsoft\Microsoft SQL Server\Instance Name\SQL. In a multi instance SQL environment we had to look for the folder that stored the registry values for our SQL Instance that, in my situation was: MSSQLSERVER. By looking at the contents of bothMSSQL.2 and MSSQL.1 folders I was able to identify that MSSQLSERVER instance was located in MSSQL.2 while SQL2005 SQL Instance was located in MSSQL.1.
- I drilled down to HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL.2\Setup, and verified that the value of the registry key Resume was set to 1. In order to trick the service pack installation, I changed the value of the Resume key to 0 and exited regedit.
- At this point, we restarted the installation of service pack, and everything went fine. The service pack installation wizard was able to detect the only component needed to be upgraded was Database Services (MSSQLSERVER), and it upgraded it successfully.
Next Steps
- As usual, direct changes or modifications to the registry should be done with extreme caution, and if possible, under the direction of a Microsoft technician. The goal of this tip was to share work around to a service pack installation error, and to avoid re-installing SQL Server from scratch.
- Check out these tips related to working with the registry:
- Check out the service pack tips for more information about maintaining a proper database platform.
About the author
Matteo Lorini is a DBA and has been working in IT since 1993. He specializes in SQL Server and also has knowledge of MySQL.This author pledges the content of this article is based on professional experience and not AI generated.
View all my tips
