Missing MSI files error during SQL Server Patching
-
Thursday, November 22, 2012 6:02 PM
I added a new node to a SQL Server failover cluster. When i was trying to update the SQL server 2008 r2 with SP2 on the New node I got an error . All the existing nodes already have SQL Server service SP2, so the new node also needs to be SP2. I am getting the missing msi file error when applying SP2 to the new node.
SQL Server Setup has encountered the following error:The cached MSI file 'C:\Windows\Installer\df540d0.msi' is missing.
Its original file is 'sql_engine_core_inst_loc.msi' and it was installed for product 'SQL Server 2008 R2 Database Engine Services'
from 'E:\en_sqlserver2008r2ent_x86_x64\1033_ENU_LP\x64\setup\sql_engine_core_inst_loc_msi\',
version '10.50.1600.1', language 'ENU'.
To resolve this problem, recover the missing file from the installation media and start setup again.
For more information about how to resolve this problem, see 'Steps to restore the missing Windows Installer cache files' (http://go.microsoft.com/fwlink/?LinkId=144387) in the Microsoft Knowledge Base.Error code 0x84B20002.
My questions are:
1) how do the msi files become missing? Are they deleted automatically or do they get deleted manually?
2) I have read articles online about how to resolve the problem. But what i need to know is how and why do the files get missing?
- Edited by SQLScript Thursday, November 22, 2012 6:50 PM
All Replies
-
Thursday, November 22, 2012 6:11 PMModerator
Hello,
Please create and run the FindSQLInstalls.vbs script that you will find on the following article:
http://support.microsoft.com/kb/969052That script will tell you what MSIs were deleted and where on the computer SQL Server setup is trying to access the original media that installed the .MSI to recreate MSI files.
This happened to me a few months ago where some of my teammates cleaned up many .MSI files and then deleted SQL Server media from a few computers.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com- Proposed As Answer by Sudeepta Ganguly Thursday, November 22, 2012 6:25 PM
- Edited by Alberto MorilloMVP, Moderator Thursday, November 22, 2012 6:40 PM
-
Thursday, November 22, 2012 6:30 PM
I had spend almost two months to fix this issue last year in most of our SQL instances during SQL Server 2005 SP4 updates.
This issue occured because the msi files were deleted from the installer folder, which was a hidden system folder.
My only guess was, a clean up script was deleting older files to free-up disk space on C: drive ;)
SKG: Please Marked as Answered, if it resolves your issue. (b:http://sudeeptaganguly.wordpress.com )
-
Thursday, November 22, 2012 6:38 PMModerator
Hello,
The bad thing about this is that once those MSI files are deleted the operating system and SQL Server instance will be on a not supported state, if you call Microsoft Support you may not receive support or they may take the case on a best effort basis.It is sad to hear the same happen to you Sudeepta.
Regards,
Alberto Morillo
SQLCoffee.com- Edited by Alberto MorilloMVP, Moderator Thursday, November 22, 2012 6:39 PM
-
Thursday, November 22, 2012 7:09 PM
Alberto,
Thanks for your response. I am a little suprised that the files were deleted from the new node i added to the SQL Server failover cluster. I did not run any cleanup jobs to delete old files on the new node which i recently added to the cluster
I added a new node to a SQL Server failover cluster. When i was trying to update the SQL server 2008 r2 with SP2 on the New node I got the error . All the existing nodes already have SQL Server service SP2, so the new node also needed to be SP2.
I am getting the missing msi file error when applying SP2 to the new node in the SQL server 2008 r2.
- Proposed As Answer by Alberto MorilloMVP, Moderator Thursday, November 22, 2012 7:25 PM
- Unproposed As Answer by Alberto MorilloMVP, Moderator Thursday, November 22, 2012 7:26 PM
-
Thursday, November 22, 2012 7:25 PMModerator
Hello,
That is normal. As soon as files are deleted from Windows\Installer folder servicing is no longer available. You won’t be able to apply any service pack or cumulative update on the instance.On my experience is a lot easier to rebuild the whole node than troubleshooting those missing MSI files.
What or who could have deleted those files? Maybe a security software, a cleanup software or maybe a teammate/coworker trying to get more free space on disk.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com- Marked As Answer by SQLScript Thursday, November 22, 2012 7:33 PM

