C Windows Installer patchcache beheerde verwijderen geschiedenis. The applications developer knows what they wish to leave cached and coorespondingly call into the. 충분할 거라 생각하고 100gb 용량으로 c 드라이브의 파티션을 나누었는데 개발 툴 이거저거 설치하다 보니 어느 샌가 빨간불이 들어왔습니다.

-->

This article describes various procedures that you can use to resolve various errors that occur when installing SQL Server service pack or a cumulative update due to corruption of windows installer cache.

Original product version: SQL Server
Original KB number: 969052

Note

The process that's described in this article provides emergency relief only and not a permanent fix. Customers who use this emergency process should validate their Windows Installer Cache using the Windows Installer Cache Verifier Package, as directed in KB article Missing Windows Installer cache requires a computer rebuild.

Symptoms

When you try to install a Microsoft SQL Server service pack or a cumulative update, you may encounter various error messages, and these may indicate Windows Installer Cache problems. The Windows Installer Cache, located in c:windowsinstaller folder, stores important files for applications installed using the Windows Installer technology and should not be deleted. If the installer cache has been compromised, you may not immediately see problems until you perform an action such as uninstall, repair, or update SQL Server.

When you install SQL Server, the Windows Installer stores critical files in the Windows Installer Cache (default is C:WindowsInstaller). These files are required for uninstalling and updating applications. Missing files cannot be copied between computers, because they are unique.

Microsoft recommends that for SQL Server installations you first use the repair process that's described in the following articles to verify your current installation:

You should run the repair from the original installation media, using the command line: setup.exe/ACTION=REPAIR/INDICATEPROGRESS=TRUE.

Repair the common shared components and features first, and then repeat the command to repair the instances installed. During the repair process, the setup dialog box disappears. As long as the progress window does not show an error, the repair process is proceeding as expected. If the installer cache file for a specific component is missing, then repair process will encounter an error.

Cause

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 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.

Resolution

To resolve these problems, use one of the following procedures.

Procedure 1.a.: Use the FixMissingMSI tool

In this procedure, you will use the FixMissingMSI tool to identify MSI and MSP files that are missing from the Windows Installer cache. As an additional step you can point the tool to the original media locations and recache the missing files.

You can download the FixMissingMSI tool from the GitHub repository.

For more information, please see SQL Setup ToolSuite Introduction (1) -FixMissingMSI.

Procedure 1.b.: Use the FindSQLInstalls.vbs script

To complete the steps in this procedure, you have to copy the FindSQLInstalls.vbs script in the FixMissingMSI folder from the GitHub repository 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. This script is used against the source locations to make sure that all MSP packages are in the Windows Installer cache directory. After executing the commands indicated in the Action needed lines in the script output file, the missing packages will be re-added if the original source media is available.

To resolve these problems by using a script, follow these steps:

Click here to go to the FindSQLInstalls.vbs raw page on GitHub.
Select all of the contents on this page, copy, and paste it to a text file. Save the text file as FindSQLInstalls.vbs.
Open an elevated command prompt to the directory to which you saved the FindSQLInstalls.vbs file, and run the command: Cscript FindSQLInstalls.vbs %computername%_sql_install_details.txt.
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.

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:

The Action needed line shows you the full path that must exist in order to update missing files for the original installation media:

Installer Cache File: C:WINDOWSInstaller19b4d2.msi

The Installer Cache File line confirms the name of the installer cache file:

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:x64setupsql_engine_core_inst_msithen 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:x64setupsql_engine_core_inst_msisql_engine_core_inst.msi' C:WINDOWSInstaller19b4d2.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: Patch LastUsedSource: n;1;c:0ca91e857a4f12dd390f0821a3HotFixSQLFiles.

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 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 insta

C Windows Installer Patchcache