Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
SQL Server 2008 setup hangs on a x64 system with more than 32 logical processors
Article ID: 2251397 - View products that this article applies to.
When you try to install a 64 bit instance of SQL Server 2008 on a system with more than 32 logical processors
(http://msdn.microsoft.com/en-us/library/dd405503%28VS.85%29.aspx), the setup process may hang. The hang may usually occur when the Setup program tries to install 32 bit components of the product (for example the setup actions that have to do with “Configuring…”). There are no error messages associated with this problem and the SQL Server setup logs will simply show incomplete execution and the only way to cancel the setup program is to kill the Setup process using task manager.
Microsoft is currently investigating this problem and will post new information as it becomes available to this article.
You can workaround the problem using one of the following methods:
Method 1: On systems running Windows Server 2008 and 2008 R2, you can affinitize
(http://msdn.microsoft.com/en-us/library/ms684251(v=VS.85).aspx)the Setup program to specific processors. To do so, run the following from an elevated command prompt on these systems:
Start /affinity ffff setup.exe
This technique does require that you run the Setup from the command line. The value ffff is a bitmap that is interpreted as a binary value, with each "on" bit (a 1 in the binary representation of the value) representing a processor to be used. So in the above example, ffff is 16 digits long in binary, each position set to 1 and it affinitizes the Setup.exe process to the first 16 processors. The value ffffffff would affinitize the Setup program to the first 32 processors, and so on.
Method 2: Before you install SQL Server 2008, temporarily change the number of logical processors to one. This makes the computer appear to be a single-processor system, and SQL Server 2008 is installed successfully. To do this, follow these steps:
Windows Server 2003
Other 32 bit applications can also exhibit this behavior (an example is SQL Server Management Studio), which can appear to be random. Occurrence depends on the processors the application is scheduled to use.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2251397 - Last Review: October 22, 2010 - Revision: 2.0