Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

On a computer that has a multicore processor, you may be unable to install SQL Server 2005


View products that this article applies to.

Symptoms

Consider the following scenario. You try to install Microsoft SQL Server 2005 on a computer that has a multicore processor, and one of the following conditions is true:
  • The ratio between logical processors and physical sockets is not a power of 2. For example, the computer has a single socket together with a triple-core processor.
  • The number of physical cores is not a power of 2.
  • The total number of CPUs is an odd number. For example, there are seven or nine CPUs.
In these scenarios, you cannot install SQL Server 2005.

↑ Back to the top


When the installation fails, the following error message is logged in the Summary.txt file:
The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
Note The Summary.txt file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG
Additionally, an error message that resembles the following is logged in the SQLSetupNum_InstanceName_SQL.log file:
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Wed Jun 18 08:32:41 2008
Service MSSQLSERVER with parameters '-m SqlSetup -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Wed Jun 18 08:32:41 2008
Unable to start service (1053)
Error Code: 0x8007041d (1053)
Windows Error Text: The service did not respond to the start or control request in a timely fashion.
Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Fri Sep 16 13:20:12 2005
Function Name: sqls::Service::Start
Source Line Number: 316
Notes
  • Num represents a four-digit number that increases for every installation of SQL Server 2005.
    InstanceName represents the name of the instance of SQL Server 2005.
  • The SQLSetupNum_InstanceName_SQL.log file is located in the following folder:
    %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files
  • This problem does not occur in Microsoft SQL Server 2008.

↑ Back to the top


Workaround

To work around this problem, use one of the following methods:

Method 1

Follow these steps before you install SQL Server 2005:
  1. Copy the setup files of the release version of SQL Server 2005 to a folder in a local drive.

    Note You must copy all the setup files that include the Servers folder and the Tools folder to a local drive.
  2. Download the SQL Server 2005 SP2 or SP3 package, and then expand it on the local drive by using the /X parameter. For example, run the following command to expand the package:
    SQLServer2005SP2-KB921896-x64-ENU.exe /X
    For more information about how to obtain SQL Server 2005 SP2 or SP3, click the following article number to view the article in the Microsoft Knowledge Base:

    913089 How to obtain the latest service pack for SQL Server 2005

  3. Note the full paths to the new .msp files in the expanded update package. For example:
    D:\temp\SP2\hotfixsql\files\sqlrun_sql.msp
  4. At the command prompt, run the Setup.exe file from the release version by using the appropriate path to involve the new .msp file in the setup.

    For example, the following command uses the update package to update the SQL Server Database Engine component to the service pack level:
    D:\temp\Servers\setup.exe HOTFIXPATCH="D:\temp\SQL2005_12Procs\SP2\hotfixsql\files\sqlrun_sql.msp"
    Note  After you complete this step, the installation of SQL Server 2005 is in a configuration that is unsupported until you have applied the SQL Server service pack.
  5. Apply the service pack package by running the setup file(s) in the expanded location. This step applies all service pack components and returns the installation of SQL Server 2005 to a supported state. 

Method 2

Before you install SQL Server 2005, temporarily change the number of logical processors to one. This makes the computer appear to be a single-processor system, and SQL Server 2005 is installed successfully. To do this, follow these steps:

Windows Server 2003

  1. To change the number of logical processors in Windows Server 2003, follow these steps:
    1. Click Start, click
      Run, type msconfig, and then click
      OK.
    2. In the System Configuration Utility dialog box, click the BOOT.INI tab.
    3. On the BOOT.INI tab, click
      Advanced Options.
    4. In the BOOT.INI Advanced Options dialog box, click to select the /NUMPROC= check box.
    5. In the list that is next to the
      /NUMPROC= check box, click 1, and then click OK.
    6. In the System Configuration Utility dialog box, click OK.
    7. Restart the server.
  2. Install SQL Server 2005.
  3. Install the latest service pack for SQL Server 2005.

    For more information about how to obtain the latest SQL Server 2005 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

    913089 How to obtain the latest service pack for SQL Server 2005

  4. Restart the server by using all the processors. To do this, follow these steps:
    1. Click Start, click
      Run, type msconfig, and then click
      OK.
    2. In the System Configuration Utility dialog box, click the General tab.
    3. On the General tab, click
      Normal Startup - load all device drivers and services, and then click OK.
    4. Restart the server.

Windows Server 2008

  1. To change the number of logical processors in Windows Server 2008, follow these steps::
    1. Click Start, click
      Run, type msconfig, and then click
      OK.
    2. In the System Configuration dialog box, click the Boot tab.
    3. On the Boot tab, click
      Advanced options.
    4. In the BOOT Advanced Options dialog box, click to select the Number of processors check box.
    5. Under the Number of processors check box, click 1, and then click OK.
    6. In the System Configuration dialog box, click OK.
    7. Restart the server.
  2. Install SQL Server 2005.
  3. Install the latest service pack for SQL Server 2005.

    Note You must install SQL Server 2005 Service Pack 2 (SP2) or a later service pack on Windows Server 2008.

    For more information about how to obtain the latest SQL Server 2005 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

    913089 How to obtain the latest service pack for SQL Server 2005

  4. Restart the server by using all the processors. To do this, follow these steps:
    1. Click Start, click
      Run, type msconfig, and then click
      OK.
    2. In the System Configuration dialog box, click the General tab.
    3. On the General tab, click
      Normal startup, and then click OK.
    4. Restart the server.

Alternate Workaround Steps


The following are conditions in which the common workaround methods are insufficient:
  • At the time that you receive the failure to start SQL Server during setup, you are presented with a Retry option. Now, replace the Sqlservr.exe and Sqlos.dll files into the BINN folder at your install location from a Service Pack 2 (SP2) installation, and then select the Retry option. This enables SQL Server to start and complete the setup.
    Note You are now in a production situation.
  • Immediately apply SQL Server SP2, and you are back in a supported configuration.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in SQL Server 2005 Service Pack 1.

↑ Back to the top


More Information

SQL Server 2005 Setup does not integrate any SQL Server 2005 service packs. To install SQL Server 2005 to a specific service pack level, you must install the release version of SQL Server 2005 first. Then, you must install the required SQL Server 2005 service pack. Therefore, although this problem is fixed in SQL Server 2005 Service Pack 1 (SP1), you still cannot install SQL Server 2005.

SQL Server 2005 Express Edition is a stand-alone package that integrates a specific SQL Server 2005 service pack. When you perform a fresh installation of SQL Server 2005 Express Edition that integrates a specific SQL Server 2005 service pack, SQL Server 2005 Express Edition is running at that service pack level. Therefore, in the scenario that is mentioned in the "Symptoms" section, you can successfully install SQL Server 2005 Express Edition together with the integrated service pack.

To download SQL Server 2005 Express Edition together with the latest SQL Server 2005 service pack, visit the following Microsoft Web site:


For more information, visit the following Microsoft Web site:

↑ Back to the top


Keywords: kb, kbprb, kbtshoot, kbexpertiseadvanced, kbsql2005error, kbsqlsetup

↑ Back to the top

Article Info
Article ID : 954835
Revision : 3
Created on : 11/20/2019
Published on : 11/20/2019
Exists online : False
Views : 616