When you try to install a Microsoft SQL Server service pack or a cumulative update, you may encounter the following error messages.
Note The following error messages can be found as text messages in the event log or in the Setup logs that are located in one of the following folders:
Error Message when the Installer Package (MSI) is missing
Error Message when the Installer Cache Package (MSP) is missing
SQL Server 2005
1636 Unable to install Windows Installer MSI file
1636 Unable to install Windows Installer MSP file
Note You must review the setup log files to identify whether any cache files are missing. For more information about how to do this, go to the "Resolution" section.
For SQL Server 2008 SP1
Collapse this tableExpand this table
Product Version
Error Message when the Installer Package (MSI) is missing
Error Message when the Installer Cache Package (MSP) is missing
SQL Server 2008 SP1
No error message
TITLE: SQL Server Setup failure. ------------------------------ SQL Server Setup has encountered the following error: The patch file cannot be opened. The file is: c:\WINNT\Installer\1cf506f.msp. Error code 0x84B20001. ------------------------------
For SQL Server 2008 SP3 build-only (CU/GDR branches are not applicable)
Collapse this tableExpand this table
Product Version
Error Message when the Installer Package (MSI) is missing
Error Message when the Installer Cache Package (MSP) is missing
SQL Server 2008 SP3
The cached MSI file 'C:\Windows\Installer\2775c8.msi' is missing. Its original file is 'sql_engine_core_inst.msi' and it was installed for product 'Microsoft SQL Server 2008 Database Engine Services' from '<network path>', version '10.3.5500.0', language 'ENU'.
The cached patch file "C:\Windows\Installer\19b19196.msp" is missing. The original file for this cached file is "sql_engine_core_inst.msp", which can be installed from "Service Pack 3 for SQL Server 2008 (KB2546951) (64-bit)", version 10.3.5500.0
Note You receive the following error message when you perform an upgrade:
Collapse this imageExpand this image
For SQL Server 2008 R2 SP1 only (CU/GDR branches are not applicable)
Collapse this tableExpand this table
Product Version
Error Message when the Installer Package (MSI) is missing
Error Message when the Installer Cache Package (MSP) is missing
SQL Server 2008 R2 SP1
TITLE: SQL Server Setup failure. ------------------------------ SQL Server Setup has encountered the following error: C:\Windows\Installer\932b909.msi. ------------------------------
The cached patch file "C:\Windows\Installer\105441.msp" is missing. The original file for this cached file is "sql_engine_core_inst_loc.msp", which can be installed from "Service Pack 1 for SQL Server 2008 R2 (KB2528583) (64-bit)", version 10.51.2500.0.
Note You receive the following error message when you perform an upgrade:
Collapse this imageExpand this image
For SQL Server 2008 R2 SP2
Collapse this tableExpand this table
Product Version
Error Message when the Installer Package (MSI) is missing
Error Message when the Installer Cache Package (MSP) is missing
SQL Server 2008 R2 SP1
The cached MSI file 'C:\Windows\Installer\932b909.msi' is missing. Its original file is 'sql_engine_core_inst.msi' and it was installed for product 'SQL Server 2008 R2 SP1 Database Engine Services' from '<network path>', version '10.51.2500.0', language 'ENU'.
The cached patch file "C:\Windows\Installer\105441.msp" is missing. The original file for this cached file is "sql_engine_core_inst_loc.msp", which can be installed from "Service Pack 1 for SQL Server 2008 R2 (KB2528583) (64-bit)", version 10.51.2500.0.
Note You receive the following error message when you perform an upgrade:
Collapse this imageExpand this image
For SQL Server 2012 prior to CU2 There is no message for missing MSP or MSI files. However, error code 1714 is logged in the Setup log.
In the Summary.txt file:
Component name: SQL Server Setup Support Files Component error code: 1714
In the Detail.txt file:
<Date><Time>Slp: Sco: File 'd:\2d5feb4dd893c4adee47f15661ac\1033_ENU_LP\x64\setup\sqlsupport_msi\x64\SqlSupport.msi' does not exist <Date><Time>Slp: Sco: File 'd:\2d5feb4dd893c4adee47f15661ac\1033_ENU_LP\x64\setup\sqlsupport_msi\x64\SqlSupport.msi' does not exist <Date><Time>Slp: Checkpoint: PREINSTALL_SQLSUPPORT_CPU64_ACTION <Date><Time>Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine <Server Name> <Date><Time>Slp: Sco: Attempting to open registry subkey Software\Microsoft\Windows\CurrentVersion\Installer <Date><Time>Slp: Sco: Attempting to get registry value InstallerLocation <Date><Time>Slp: Windows installer version : 5.0.7601.17514 <Date><Time>Slp: Sco: Waiting for service 'msiserver' to accept the stop request. <Date><Time>Slp: Sco: Attempting to open SC Manager <Date><Time>Slp: Sco: Attempting to open service handle for service msiserver <Date><Time>Slp: Invoking QueryServiceStatus Win32 API <Date><Time>Slp: Sco: Attempting to close service handle for service msiserver <Date><Time>Slp: Sco: Attempting to close SC Manager <Date><Time> Slp: Target package: "d:\2d5feb4dd893c4adee47f15661ac\1033_ENU_LP\x64\setup\sqlsupport_msi\SqlSupport.msi" <Date><Time> Slp: MSI Error: 1714 The older version of Microsoft SQL Server 2012 Setup (English) cannot be removed. Contact your technical support group. <Date><Time> Slp: InstallPackage: MsiInstallProduct returned the result code 1603. <Date><Time> Slp: Using MSI error code to detect the retry option: 1714 <Date><Time> Slp: No retry-able MSI return code detected.
For SQL Server 2012 CU2 (and any subsequent CU or SP)
Collapse this tableExpand this table
Product Version
Error Message when the Installer Package (MSI) is missing
Error Message when the Installer Cache Package (MSP) is missing
SQL Server 2008 R2 SP1
The cached MSI file 'C:\Windows\Installer\<file_encoded_name>.msi' is missing. Its original file is ''C:\Windows\Installer\sql_<featurename>.msi' }' and it was installed for product 'Microsoft SQL Server <version>' from 'C:\originalfolder', version '<versionnumber>', language '<language>'.
The cached patch file "c:\Windows\Installer\1fdb1aec.msp" is missing. Its original file is "sql_engine_core_inst.msp", which can be installed from "Hotfix 2316 for SQL Server 2012 (KB2679368) (64-bit)", version 11.00.2100.60.The cached patch file “C:\Windows\Installer\<file_encoded_name>.msp' is missing. Its original file is ''C:\Windows\Installer\sql_<featurename>.msp' }', which can be installed from ‘Hotfix <number> for SQL Server 2012 <KB number>’, version '<versionnumber>'.
These problems may occur when the Windows Installer database file (.msi) or the Windows Installer patch file (.msp) is missing from the Windows Installer cache. The Windows Installer cache is located in the following folder:
%windir%\installer
When a product is installed by using Windows Installer, a stripped version of the original .msi file is stored in the Windows Installer cache. Every update to the product such as a hotfix, a cumulative update, or a service pack setup, also stores the relevant .msp or .msi file in the Windows Installer cache.
Any future update to the product such as a hotfix, a cumulative update, or a service pack setup, relies on the information in the files that are stored in the Windows Installer cache. Without this information, the new update cannot perform the required transformations.
To resolve these problems, use one of the following procedures.
Procedure 1: Use a script
To complete the steps in this procedure, you have to copy the FindSQLInstalls.vbs script from the "More Information" section to a local folder on the computer where you are trying to update your SQL Server installation.
Note The FindSQLInstalls.vbs script collects the information to correct invalid package paths. And, this script is used against the source locations to make sure that all MSP packages are in the Windows Installer cache directory. Any missing packages will be re-added if the original source media is available.
To resolve these problems by using a script, follow these steps:
Locate the directory to which you saved the script content.
Open an elevated command prompt to the directory to which you saved the script, and run the following command:
Open the file from step 2 in a text editor such as Notepad, and identify the problems that are causing the failure. To do this, search the text file for string patterns such as the following:
do not
!!!
Based on the results in step 3, take the steps that are required.
Note Look for more information about these steps in the "Examples" section.
Repeat steps 2 through 4 until the text file that is created in step 2 no longer contains text that references invalid paths or missing files for the component that is being updated.
Examples
The following examples are entries and explanations of actions that are outlined in the output file that is generated when you run the FindSQLInstalls.vbs script.
Example 1: Missing installer files
The following is an example of the output that is generated when you are missing an .msi package in the Windows Installer cache folder.
================================================================================
PRODUCT NAME : Microsoft SQL Server 2008 Database Engine Services
================================================================================
Product Code: {9FFAE13C-6160-4DD0-A67A-DAC5994F81BD}
Version : 10.2.4000.0
Most Current Install Date: 20110211
Target Install Location:
Registry Path:
HKEY_CLASSES_ROOT\Installer\Products\C31EAFF906160DD46AA7AD5C99F418DB\SourceList
Package : sql_engine_core_inst.msi
Install Source: \x64\setup\sql_engine_core_inst_msi\
LastUsedSource: m;1;G:\x64\setup\sql_engine_core_inst_msi\
The "LastUsedSource" line points to the location that was used to run the Setup program.
In the "LastUsedSource" line, the m; entry signifies media and indicates that the original source is CD/DVD media.
In the following example, the source is a CD or a DVD in drive G. If the installation occurred from a file folder or from a network share, the "LastUsedSource" line begins with an n; entry, followed by a Numeric_Data_Name; entry, and then the actual path:
!!!! sql_engine_core_inst.msi DOES NOT exist on the path in the path G:\x64\setup\sql_engine_core_inst_msi\ !!!!
Action needed, re-establish the path to G:\x64\setup\sql_engine_core_inst_msi\
The "Action needed" line shows you the full path that must exist in order to update missing files for the original installation media:
The "Installer Cache File" line confirms the name of the installer cache file:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!! C:\WINDOWS\Installer\19b4d2.msi DOES NOT exist in the Installer cache. !!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
The following section of the output advises you of actions that are required to resolve the missing files:
Action needed, recreate or re-establish path to the directory:
G:\x64\setup\sql_engine_core_inst_msi\then rerun this script to update installer cache and results
The path on the line above must exist at the root location to resolve
this problem with your msi/msp file not being found or corrupted,
In some cases you may need to manually copy the missing file or manually
replace the problem file overwriting it is exist:
Copy "G:\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi" C:\WINDOWS\Installer\19b4d2.msi
Replace the existing file if prompted to do so.
Example 2: Missing patches
Missing patches may result in entries that resemble those in Example 1. Most of the time, you will notice entries in the "Patch LastUsedSource" line that reference a patch, and this line resembles the following:
This output indicates the following about the patch installation:
The original patch was installed by double-clicking the patch's executable file.
The installer for the patch used a temp folder, c:\0ca91e857a4f12dd390f0821a3, during installation of the patch.
To re-create the path, you must run the same executable and add the following parameter:
/x:c:\0ca91e857a4f12dd390f0821a3
Note This command forces the executable to extract the files to the previous missing location, and this re-creates the structure that is required to update the Windows installer cache with any missing files. The actual location will vary, and a single patch such as a service pack may have to be extracted to multiple locations. Each installed product includes a section that contains the following information for "Patches Installed":
The "KB Article URL" line can help you download any patch media, if this is necessary.
Procedure 2: Manually restore the files
To manually restore the files that are missing from the Windows Installer cache, follow these steps:
Collect the complete details about the missing file from the error message, from the setup log file, or from the registry entries that are maintained by the Windows Installer. For example, in Error Message 1 in the "Symptoms" section, all the information that is required to resolve the issue is present in the error message:
PatchName: "Hotfix 1702 for SQL Server 2008 R2 (KB981355) (64-bit)"
Original MSP file that is used by the Patch: sql_engine_core_inst.msp
, and search for the KB article that is associated with this patch. In this example, you must search for KB981355.
Download this patch package to your computer. Make sure that you download the patch package that corresponds to the required platform. In this example, the package is SQLServer2008R2-KB981355-x64.exe.
Extract the contents of the patch package by using the following syntax:
Copy this original msp file to the following Windows Installer cache:
%windir%\installer\
Rename the original msp file, sql_engine_core_inst.msp, to the following name:
cached msp file 1fdb1aec.msp
You can start the Setup program for the update that resulted in the error and resume the update process. You may encounter this message for a missing Windows Installer cache file for another component or for another update of the same product.
To obtain a list of all the missing Windows Installer cache files that are related to the SQL Server product components, you can download the SQL Server 2008 R2 BPA tool that is mentioned in the "More Information" section.
If the error message references a missing Windows Installer database file (.msi), you do not have to perform steps 2 through 4. Instead, you can go directly to step 5. You have to locate the .msi from the original media that you used to install the product. If this error message was generated for sql_engine_core_inst.msi, then you have to locate this file from the setup media under the following folder structure:
\x64\setup\sql_engine_core_inst_msi\
The other steps are the same.
More information for Procedure 2
How to find the patch package and the product details for a missing .msp file
Different versions of the product generate different error messages for this problem. The error messages that are mentioned in the "Symptoms" section appear for Setup programs for updates starting with Microsoft SQL Server 2008 SP1. For other updates, you receive error messages that may not clearly specify which patch file is missing from the Windows Installer cache and the specific update details. For these error messages, the setup log files will contain information about the missing Windows Installer cache file. A sample setup log resembles the following:
MSI (s) (FC:F8) [13:48:58:649]: Opening existing patch 'C:\WINDOWS\Installer\145258.msp'.
MSI (s) (FC:F8) [13:48:58:649]: Couldn't find local patch 'C:\WINDOWS\Installer\145258.msp'. Looking for it at its source.
MSI (s) (FC:F8) [13:48:58:649]: Resolving Patch source.
MSI (s) (FC:F8) [13:48:58:649]: Note: 1: 2203 2: D:\cda162709d239766830bae5ce12b\HotFixSQL\Files\sqlrun_sql.msp 3: -2147287037
MSI (s) (FC:F8) [13:48:58:649]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (FC:F8) [13:49:29:961]: Product: Microsoft SQL Server 2005 -- Installation failed.
MSI (s) (FC:F8) [13:49:29:992]: MainEngineThread is returning 1635
This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
D:\SQL2K5\Servers\Setup\SqlRun_SQL.msi
If you examine this setup log carefully, it already gives you the information about the Original MSP file that was used by the following patch:
sqlrun_sql.msp
To find more details about the missing .msp file in the Windows Installer cache, follow these steps:
Search for the missing .msp file in the following Windows Installer Patches registry subkey:
For the sample setup log, the information about the missing .msp file and its corresponding patch details are present in the following registry entries:
Value: 6
Name: DisplayName
Data: GDR 2050 for SQL Server Database Services 2005 ENU (KB932555)
Now you have all the information points to start the steps to resolve the missing files in the Windows Installer cache.
Note If you use Microsoft SQL Server 2008 Service Pack 3 (SP3) or a later version, you can also receive a similar error message for the missing .msi files. By using this error message, you can quickly determine which file is missing, what service pack to download, and where you can find the download.
For more information about how to obtain the service pack, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table:
Collapse this tableExpand this table
Rule software
Rule title
Rule description
Product versions against which the rule is evaluated
SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)
Setup - Installer cache is missing for the SQL Installation
The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect Missing Installer cache file for SQL Server components. The SQL Server 2008 R2 BPA supports both SQL Server 2008 and SQL Server 2008 R2. If you run the BPA tool and encounter an Error with the title of Setup - Installer cache is missing for the SQL Installation, and then the cache files are missing from the cache folder.
SQL Server 2008 SQL Server 2008 R2
SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA)
Setup - Installer cache is missing for the SQL Installation
The SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect Missing Installer cache file for SQL Server components.If you run the BPA tool and encounter an Error with the title of Setup - Installer cache is missing for the SQL Installation,and then the cache files are missing from the cache folder.