This situation happened in a Windows 2008 R2 Enterprise X64 environment, when attempting to apply the Service Pack 2 R2 on a Clustered Microsoft SQL Server 2008 R2 Instance.
Missing files scenario may occur when your Windows Server environment have gone under some of these circumstances ( examples):
- Intentional deletion of install files from C\Windows\Installer folder
- Security breach and malicious attempt to harm the system
- A batch program running periodically to clear old files to reclaim disk space (this was my case)
There are 2 types of files used by MSSQL Setup: MSI (Windows installer database file) and MSP(Windows Installer Patch Files). Whenever some of these are missing (are there are many), setup will throw an error or if not, will inform some is missing and give the user a chance to re-enter the correct folder where it is located.
The errors are:
TITLE: SQL Server Setup failure. The cached MSI file ‘C:\Windows\Installer\3bee658c.msi’ is missing. Its original file is ‘sql_fulltext.msi’ and it was installed for product ‘SQL Server 2008 R2 SP2 Full text search’ from ‘F:\MSSQLInstall\SQL2008_R2_x64\x64\setup\’, version ‘10.52.4000.0’, language ‘ENU’. To resolve this problem, recover the missing file from the installation media and start setup again.
This one prevents the Service Pack setup to start
This other is an example that occurs after the patching has already started.
Fortunately there is KB article from Microsoft address the resolution steps.
I have opted for the script solution, which turned out to be successful after some attempts. Note that after the steps followed and some folders were recreated, the Service Pack 2 R2 appliance still accused some missing files, but even so the patching terminated with success.
The script is named “FindSQLInstalls.vbs”. It will go through all SQL related setup and patches installed and point out what is missing, with the fix instructions.
The above picture illustrates the importance of having the MSP and MSI files in the windows installer cache. They are required for upcoming patches and hotfixes. Full text with this explanation is listed in the Microsoft KB.