This article describes the following about this hotfix release:
The issues that are fixed by this hotfix package
The prerequisites for installing the hotfix package
Whether you must restart your computer after you install the hotfix package
Whether you must make any registry changes
The Microsoft SQL Server 2005 Setup program may take much longer than expected to finish running. Sometimes this period will be more than 24 hours.
You may see in the detailed SQL Server Windows Installer log that most of the execution time occurs in the Write_sqlXXX custom actions. These custom actions may include the following:
Note This problem may occur when you install software that also installs SQL Server 2005, such as Microsoft System Center Data Protection Manager (DPM) 2007.
When the primary domain has many external trust relationships with other domains, or when many lookups are performed at the same time, the time that is required to look up domain group names may increase significantly. Therefore, the time that is required to install SQL Server 2005 may also increase.
How to obtain the hotfix
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
There are no prerequisites for this hotfix.
You do not have to restart the computer after you apply this hotfix.
You do not have to change the registry after you apply this hotfix.
How to apply the hotfix
You can apply the hotfix files together with your installation files for SQL Server 2005. By doing this, SQL Server Setup first merges the hotfix files together with the setup files that come from the SQL Server 2005 installation media. Then, the Setup program starts an installation that avoids the problem. To do this, follow these steps:
Extract the hotfix package file into a folder.
You obtain some .exe files that resemble the following files:
At a command prompt, run these .exe files by specifying the /X switch to extract these .exe files into different folders.
Note In this command, <SQLInstall> is a placeholder for the name of the folder that contains the SQL Server 2005 installation media. The <OtherParameters> placeholder represents the additional parameters that you specify.
To work around this issue, use one of the following methods.
Temporarily disable the network on the computer on which the SQL Server 2005 Setup program is running. To do this, either disconnect the network cable or type the following command at a command prompt:
Note If you are installing a SQL Server failover cluster, this workaround will not work.
Follow the steps in the following Microsoft Knowledge Base article to restrict the lookup of isolated names in external trusted domains:
818024 How to restrict the lookup of isolated names in external trusted domains by using the LsaLookupRestrictIsolatedNameLevel registry entry
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem may also occur when you install DPM 2007. When you install DPM 2007, it may take a very long time to install SQL Server 2005. Because the DPM 2007 installer installs SQL Server 2005 from DPM 2007 DVD media, we do not recommend that you perform a slipstream installation of SQL Server 2005 by using this hotfix. Use Method 1 in the "Workaround" section when the DPM 2007 installer starts to install SQL Server 2005.
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems, Microsoft SQL Server 2005 Enterprise X64 Edition, Microsoft SQL Server 2005 Express Edition, Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Standard X64 Edition, Microsoft SQL Server 2005 Workgroup Edition, Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems