You cannot install SQL Server 2005 Service Pack 2 when the database file of the Resource database is not in the same folder as the log file of the Resource database

Extended support for SQL Server 2005 ended on April 12, 2016

If you are still running SQL Server 2005, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
You cannot install Microsoft SQL Server 2005 Service Pack 2 (SP2). Additionally, the following error message is logged in the Summary.txt file:
Product : Database Services (InstanceName)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29534
Error Description : MSP Error: 29534 Service 'MSSQL$InstanceName' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly.
Note The Summary.txt file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\Log\Hotfix
This problem may also happen when you install a cumulative update or a hotfix to SQL Server 2005.

This problem occurs when the database file of the Resource database (Mssqlsystemresource.mdf) is not in the same folder as the log file of the Resource database (Mssqlsystemresource.ldf).
Cause
This problem occurs because SQL Server 2005 SP2 Setup and the hotfix installers require that the database file of the Resource database is in the same folder as the log file of the Resource database.
Workaround
To work around this problem, move the log file of the Resource database to the same folder as the database file of the Resource database. Then, start the Setup program again.

For more information about how to move the log file of the Resource database, see the "Moving the master and Resource Databases" section of the following Microsoft Developer Network (MSDN) Web site:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 947989 - Last Review: 11/01/2013 22:25:00 - Revision: 3.0

Microsoft SQL Server 2005 Service Pack 2

  • kbnosurvey kbarchive kbexpertiseadvanced kbtshoot kbprb KB947989
Feedback