Product Version (Previous): 5000
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2463332_sqlrun_sql.msp.log
Error Number : 29534
Error Description : MSP Error: 29534 Service 'MSSQL$INSTANCE' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1814) The specified resource name cannot be found in the image file.
When the problem occurs, error messages that resemble the following are logged in the SQL Server error log file:
2011-02-20 02:33:48.99 spid7s CREATE FILE encountered operating system error 3(error not found) while attempting to open or create the physical file 'X:\ \MSSQL2005\MSSQL.1\MSSQL\Data\tempdb.mdf'.
2011-02-20 02:33:49.22 spid7s Error: 17207, Severity: 16, State: 1.
2011-02-20 02:33:49.22 spid7s FCB::Open: Operating system error 3(error not found) occurred while creating or opening file 'X:\MSSQL2005\MSSQL.1\MSSQL\Data\tempdb.mdf'. Diagnose and correct the operating system error, and retry the operation.
2011-02-20 02:33:49.22 spid7s Error: 17204, Severity: 16, State: 1.
2011-02-20 02:33:49.22 spid7s FCB::Open failed: Could not open file X:\MSSQL2005\MSSQL.1\MSSQL\Data\tempdb.mdf for file number 1. OS error: 3(error not found).
2011-02-20 02:33:49.27 spid7s Error: 5120, Severity: 16, State: 101.
2011-02-20 02:33:49.27 spid7s Unable to open the physical file "x:\MSSQL2005\MSSQL.1\MSSQL\Data\tempdb.mdf". Operating system error 3: "3(error not found)".
2011-02-20 02:33:49.37 spid7s Error: 1802, Severity: 16, State: 4.
2011-02-20 02:33:49.37 spid7s CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2011-02-20 02:33:49.37 spid7s Error: 5123, Severity: 16, State: 1.
2011-02-20 02:33:49.37 spid7s CREATE FILE encountered operating system error 3(error not found) while attempting to open or create the physical file 'X:\MSSQL2005\MSSQL.1\MSSQL\Data\tempdb.mdf'.
2011-02-20 02:33:49.37 spid7s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
Additionally, the service state for both SQL Server service and SQL Server Agent service is changed to "Stopped" state. When you restart the affected services manually, the version is incorrectly displayed as 9.00.5000.00, the version corresponding SQL Server 2005 Service Pack 4, though the installation did not complete successfully.
During the installation of Service Pack 4 for SQL Server 2005, the setup program tries to start SQL Server with minimal configuration using –f startup option. This step fails when the default location is invalid as SQL Server cannot create tempdb database using the default location.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Step 1: Set the default data directory value and the default log directory value to valid folder paths
You can set the default data directory value and the default log directory value by using either SQL Server Management Studio or Registry Editor.
Method 1: Use SQL Server Management Studio
- In Object Explorer, right-click a server and click Properties
- In the left panel, click the Database settings page.
- In Database default locations, view the current default locations for new data files and new log files. To change a default location, enter a new default pathname in the Data or Log field, or click the browse button to find and select a pathname.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
- Start Registry Editor (Regedt32.exe) from the command line.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<MSSQL.x>\MSSQLServer
Note In this registry subkey, <MSSQL.x> represents the corresponding value for your system. To obtain this value, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\
- In the right panel, click the DefaultData registry entry and enter a valid path (if it is pointing to an incorrect location).
- In the right panel, click the DefaultLog registry entry and enter a valid path (if it is pointing to an incorrect location).
Step 2:Retry the installation of Service Pack 4 for the affected instance.
Note: The setup program will show that the instance has already been upgraded and it will not allow you to select just the "Database Services" component. You need to select all the features for that instance for the setup program to proceed.
Artikelnummer: 2565113 – Letzte Überarbeitung: 20.07.2011 – Revision: 1