- 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
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:
How to obtain the hotfixA 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.
PrerequisitesThere 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 hotfixYou 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.
For example, run the following commands:AS2005-KB901530-x86-ENU.exe /X:C:\QFE\ASAfter you extract these .exe files, the .msp files appear in the following folders:
- Install SQL Server 2005 by running a command that resembles the following:<SQLInstall>\Servers\setup.exe SQLSUPPORTPATCH="C:\QFE\SqlSupport\msp\SqlSupport.msp" HOTFIXPATCH="C:\QFE\AS\hotfixas\files\sqlrun_as.msp;C:\QFE\SQL\hotfixsql\files\sqlrun_sql.msp;C:\QFE\IS\hotfixdts\files\sqlrun_dts.msp;C:\QFE\NS\hotfixns\files\sqlrun_ns.msp;C:\QFE\RS\hotfixrs\files\sqlrun_rs.msp;C:\QFE\Tools\hotfixtools\files\sqlrun_tools.msp" <OtherParameters>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.
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:
Follow the steps in the following Microsoft Knowledge Base article to restrict the lookup of isolated names in external trusted domains:
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:
Article ID: 910070 - Last Review: Mar 29, 2017 - Revision: 3