This article describes how to update or slipstream a failed installation of Microsoft SQL Server 2008 by using the latest Cumulative Update (CU) or latest Service Pack (SP). Use these instructions when you cannot install SQL Server 2008 because of a known issue in the Setup program. The "SQL Server 2008 Setup hotfixes" section lists the Microsoft Knowledge Base articles that describe known setup issues and explains how to obtain the latest update.
There are two situations to consider:
- You attempt to install SQL Server 2008. You encounter a setup failure, and the setup files are installed on the computer.
- You want to proactively avoid known setup issues by using an update setup.
It is recommend that you update or slipstream the original SQL Server 2008 by using Service Pack 1 because Service Pack enables to update the entire product. A CU that is based on the original SQL Server 2008 release can only update the SQL Support component.
For answers to frequently asked questions about slipstreaming, see the SQL Server 2008 Slipstream Frequently Asked Questions
topic on the following Microsoft Web site:
When you run the original release version of SQL Server 2008 Setup, the Setup program copies itself on the local computer, and then re-runs from the local copy. Therefore, if there is a later version of the support files on the computer, the Setup program will run these updated files. Therefore, you can update the SQL Server 2008 Setup support files before you run the Setup.exe file.
Starting from SQL Server 2008 Service Pack 1, you can update SQL Server 2008 by using the slipstream infrastructure. When you install Service Pack 1 by using the slipstream procedure or install to an existing SQL Server 2008 installation, an entry is created for the Service Pack in Add or Remove Programs. You can uninstall the service pack by using this entry.
To verify whether a service pack is installed correctly, run the SQL Discovery report that is available in the SQL Server 2008 Installation Center. You should see the features are version 10.n
, where n
represents the service pack version. For example, 10.1.xxxx
represents Service Pack 1.
How to update an installation of SQL Server 2008
When you try to install SQL Server 2008 from a DVD or from a network share, the installation fails because of an issue with the release version of the Setup program.
The following steps describe how to update SQL Server 2008 Setup when a Setup issue occurs:
- If the SQL Server 2008 Setup support files are installed on the computer, you apply a CU or a hotfix to update the SQL Server 2008 Setup support files, and then rerun the Setup program from the DVD or the network share.
- If the SQL Server 2008 Setup support files are not installed, see the "Proactively running setup" section.
To determine whether the SQL Server 2008 Setup support files are installed on the computer, view the entry by using Add or Remove Programs
in Control Panel in operating systems that are earlier than Windows Vista. In Windows Vista or later versions of Windows, view the entry by using Programs and Features
in Control Panel. To apply a CU or a hotfix and run the Setup program, follow these steps:
- If a fix is available through a hotfix, download the CU or the hotfix, and then install it on the computer by running the .exe file or by using the command line. The package detects the SQL Server 2008 Setup support files on the computer and then applies a new version of the SQLSupport.msi file.
- Run the Setup program again from the DVD or from the network share. The Setup program detects that a later version of the SQLSupport.msi file is available on the computer, and the Setup program runs from the local version on the computer instead of from the DVD or network share.
The following limitations apply when you update the Setup program or use the slipstream procedure:
- Important You must uninstall a failed installation if the Summary.txt log file indicates that you must uninstall.
- If you use the slipstream procedure to upgrade an installation to a Wow64 installation, you must perform one of the following additional steps:
- Specify the /Action parameter on the command line in addition to the /x86 parameter.
- On the Options page of the Installation Center, select x86.
- If you add features to an instance that already has the database service installed through slipstreaming, the installation may fail. To work around this issue, you need to add feature by using the original SQL Server 2008 source media or upgrade the instance to SP1 and then use the slipstream infrastructure.
- When you copy slipstream packages, use paths that do not contain spaces. If you specify a location that contains spaces for either /PCUSOURCE or /CUSOURCE parameters, a failure occurs with slipstream setup.
Proactively running setup
There are two methods that
you can use to update an installation of SQL Server 2008. We recommend that you use the first method because of the following benefits of the slipstream infrastructure:
- You can quickly update to SQL Server 2008 SP1 in a single installation.
- Reduce the restart times.
- Improve the overall setup experience.
- Avoid known setup issues.
To use these methods, the administrator must obtain the updated SQL Server 2008 Setup support files by downloading the latest CU or hotfix, or service pack. For information about the Setup fixes that are included in the latest hotfix and for information about how to download the hotfix, see the "SQL Server 2008 Setup hotfixes" section. After you obtain the updated SQL Server 2008 Setup support files, use one of the following methods.
Use the slipstream procedure to update SQL Server 2008
This method allows you to update the entire product when you run the SQL Server 2008 Setup program after following one of the following procedures:
Procedure 1: Basic slipstream steps
Follow the following steps to create a slipstream drop that you can use for installing the original media and a service pack at the same time.
- Install the following prerequisites for SQL Server 2008.
- Download the service pack package that matches you system architecture. For example download the x64 package of SQL Server 2008 Service Pack 1 if your system is an x64-based system.
- Extract the service pack by running the following command:
- Run the service pack to install Setup files on the computer. You will receive a Setup Support Files dialog box if the Setup support files have not been installed.
You can also run the following file to install the setup support files:
- Run the Setup.exe file from the SQL Server 2008 source media by specifying the /PCUSource parameter. For example:
Procedure 2: Create a merged drop:
This procedure describes how to create a new source media that will slipstream the original source media and SQL Server 2008 Service Pack 1. When you create this merged drop, you can install SQL Server 2008 SP1 in a single step.Notes
- It is recommended that you first complete a slipstream installation from the new drop on a test computer before you deploy it into the production environment.
- These steps are for the English version of SQL Server 2008. However, it works for any language of SQL Server 2008 if you obtain the correct language of service pack package.
- Copy the original SQL Server 2008 source media to c:\SQLServer2008_FullSP1.
- Download the Service Pack 1 package. The package names are as follows:
- Extract the packages as follows:
Note Make sure that you complete this step for all architectures to ensure the original media is updated correctly.
- SQLServer2008SP1-KB968369-IA64-ENU.exe /x:c:\SQLServer2008_FullSP1\PCU
- SQLServer2008SP1-KB968369-x64-ENU.exe /x:c:\SQLServer2008_FullSP1\PCU
- SQLServer2008SP1-KB968369-x86-ENU.exe /x:c:\SQLServer2008_FullSP1\PCU
- Run the following commands to copy the Setup.exe file and the Setup.rll file from the extracted location to the original source media location.
robocopy C:\SQLServer2008_FullSP1\PCU c:\SQLServer2008_FullSP1 Setup.exe
robocopy C:\SQLServer2008_FullSP1\PCU c:\SQLServer2008_FullSP1 Setup.rll
- Run the following commands to copy all files (not the folders), except the Microsoft.SQL.Chainer.PackageData.dll file, in C:\SQLServer2008_FullSP1\PCU\Architecture to C:\SQLServer2008_FullSP1 \Architecture to update the original files.
robocopy C:\SQLServer2008_FullSP1\pcu\x86 C:\SQLServer2008_FullSP1\x86 /XF Microsoft.SQL.Chainer.PackageData.dll
robocopy C:\SQLServer2008_FullSP1\pcu\x64 C:\SQLServer2008_FullSP1\x64 /XF Microsoft.SQL.Chainer.PackageData.dll
robocopy C:\SQLServer2008_FullSP1\pcu\ia64 C:\SQLServer2008_FullSP1\ia64 /XF Microsoft.SQL.Chainer.PackageData.dll
Note If you accidentally copy the Microsoft.SQL.Chainer.PackageData.dll file, you may receive the following error message when you run the Setup.exe file.
SQL Server Setup has encountered the following error:
The specified action LandingPage is not supported for the SQL Server patchingg operation.
Error code 0x84BF0007
If this issue occurs, restore the Microsoft.SQL.Chainer.PackageData.dll file back to the original version.
- Determine if you have the Defaultsetup.ini file in the following folders:
If you have the Defaultsetup.ini file in the folders, open the Defaultsetup.ini file, and then add PCUSOURCE=".\PCU" to the file as follows:
If you do not have the Defaultsetup.ini file in the folders, create the Defaultsetup.ini file in the folders, and add the following content to the file:
;SQLSERVER2008 Configuration File
Note This file tells the Setup program where to locate the SP1 source media that you extracted in step 3.
;SQLSERVER2008 Configuration File
- Start the Setup program.
You should not perform the slipstream procedure to apply SQL Server 2008 Service Pack 1 for the SQL Server 2008 Express edition. SQL Server 2008 Express Edition SP1 is already a merged drop. However, you can use the slipstream procedure to apply a cumulative update for the SQL Server 2008 Express edition.
How to verify if you have completed a slipstream update
- In the Installation Rules page, an Update Setup Media Language Rule item is shown in the rules list.
- In the Ready to Install page, the Action node indicates that it is a slipstream install. Additionally, a Slipstream node is shown in the list.
In the Summary log file, you can find the PCUSource setting.
- After the installation, if you run the SQL Server features discovery report from the Installation Center, you should see the features are version 10.1.xxxx.
Update the SQL Server 2008 Setup support files
There are two options that you can use to install the SQL Server 2008 Setup support files. We recommend that you use this method to install SQL Server 2008 Setup support files before SQL Server SP1.Note
For the two options, only the SQL Server 2008 Setup support files are update. To update the entire product, you must run the hotfix package after the product has been successfully installed.
Option 1: Install the SQLSupport.msi file directly
This option is best for running a patched setup on a small number of computers.
- Install any prerequisite components for SQL Server 2008 if they are not already installed. Microsoft Windows Installer 4.5 must be installed. You must install the .NET Framework 2.0 SP2 for SQL Server 2008 Express Edition and the .NET Framework 3.5 SP1 for other editions. You must download the .NET Framework 3.5 SP1 from the internet and apply the SP1 manually.
- Double-click the hotfix package to install the SQL Server 2008 Setup support files. After you extract the contents of the package, the updated SQL Server 2008 Setup support files will be installed. The hotfix package will complete the installation without notifying you when it is completed. To confirm that the files are installed, view the entry by using the Add or Remove Programs item in Control Panel in operating systems that are earlier than Windows Vista. In Windows Vista or later versions of Windows, view the entry by using the Programs and Features item in Control Panel.
- Start the Setup program from the DVD or from the network share.
Option 2: Update the original media files
This option is best for running a patched setup on a large number of computers, large deployments, or when an administrator wants to make available this patched setup to users. It is important to follow these steps carefully and fully test before making this option available to others.
- Download the hotfix that includes the updated SQL Server 2008 Setup support files that you want to use to update the original media files. You must download the hotfixes for x86, x64, and IA-64 platforms because the original media contains the files for each platform.
- At a command prompt, type the following command, and then press ENTER to extract the contents of the package:
hotfix_package_name/x:c:\kb _number_of_hotfix package\architecture The architecture placeholder represents the different hardware platforms. For example, it can represent one of the following folders:The following examples represent how you can use this command:
- SQLServer2008-KB956717-IA64.exe /x:c:\kb956717\ia64
- Copy the contents of the SQL Server 2008 DVD to the local hard disk.
- Copy the following files:
- Copy the Setup.exe and Setup.rll files from the C:\kb_number_of_hotfix package\ folder to the Folder that contains the local copy of media\ folder.
- Copy all files (not the sub-folders) in the architecture folder, except the Microsoft.SQL.Chainer.PackageData.dll file, from the C:\kb_number_of_hotfix package\architecture\architecture\ folder to the Folder that contains the local copy of media\architecture\ folder.
- Start the Setup program from the local folder.
Due to schema changes that have been introduced in RTM based-cumulative update packages for SQL Server 2008 that start with Cumulative Update Package 8, you may receive the following error message when you run the Setup program. You may receive the following error message after you update the Setup support files by using the procedure that is described in option 2:
2010-01-14 15:34:36 Slp: Exception type:
2010-01-14 15:34:36 Slp: Message:
2010-01-14 15:34:36 Slp: The 'Path' attribute is not declared.
To avoid this validation issue, we recommend that you copy the Microsoft.SQL.Chainer.PackageData.dll file from the RTM media and keep the original Microsoft.SQL.Chainer.Package.dll file in the same location as the Microsoft.SQL.Chainer.Package.Package.xsd file. Do this to make sure that the two .dll files are in sync. This combination of .dll files will install the RTM version of SqlSupport.msi (10.00.1600.22). To benefit from the bug fixes that are present in the cumulative update, use one of the following methods:
Manually install the SQL Support .msi file for the particular architecture from the following cumulative update package extraction location:
In addition to the to the files that are listed in step 4 in option 2, the files that are described in the following steps should be copied before you start setup from a local folder. To copy the files, following these steps.
- Copy the Microsoft.SQL.Chainer.Package.dll file from the RTM folder to the local copy of the <media>\<architecture folder> folder.
- Copy the Sqlsupport.msi file. Of the following locations, copy the file from the first location to the local copy of the second location:
SQL Server 2008 setup hotfixes
For more information about known setup issues and the fixes to resolve these issues, click the following article numbers to view the articles in the Microsoft Knowledge Base:
FIX: Error message when you install SQL Server 2008 Express edition on a domain controller that is running Windows Server 2003 Service Pack 2 or Windows Small Business Server 2003 Service Pack 1: "Exception has been thrown by the target of invocation"
FIX: You cannot upgrade a non-English instance of SQL Server 2000 Reporting Services to SQL Server 2008 Reporting Services
FIX: When you install SQL Server 2008, the installation fails, and the "Attributes do not match" error message is logged in the Summary.txt file
FIX: SQL Server Setup does not use the instance name that you provide in the modified Config.ini file when you try to install SQL Server 2008 Express
FIX: Cluster upgrade to SQL Server 2008 fails when SQL Server 2005 cluster nodes have different installed features
FIX: The CompleteFailoverCluster action does not detect the correct SKU that is prepared by using the PrepareFailoverCluster action in SQL Server 2008
FIX: Error message when you try to add a second node to a SQL Server 2008 failover cluster: "The current SKU is invalid"
If other setup issues are identified, additional Microsoft Knowledge Base articles will be released and included in this list.
How to obtain setup hotfixes for SQL Server 2008
A supported cumulative update package is now available from Microsoft. However, it is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems. This cumulative update package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for the next SQL Server 2008 service pack that contains the hotfixes in this cumulative update package.
For more information about the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative update package 1 for SQL Server 2008