The cached msi file is missing

You understand what it’s choose, you are running a service fill on SQL Server and 99.9% of the moment it all runs smoothly however that odd 0.1% of the time once it doesn’t is commonly in the middle of the night with no one approximately to contact on.

You watching: The cached msi file is missing

Well to spare you some pain I’ve found a really cool energy to help mitigate hazard.

I was newly doing a company load, I’d run it on the entire test estate and fifty percent of the Production estate, I’d used Pinal Dave’s really advantageous AG inspect list and also been really overcareful, I’d finimelted integrity checks on all databases, I’d backed whatever up and also even had actually a picture of the server completed.

When I clicked on the company load I got the error “missing MSI” sorry I don’t have actually the display dump or the complete error message because at the moment of trying to fix it I did’t think to take a copy ☹

I understand the prime factor for this happening is that the installer documents had been removed.

Anymethod after a lot of bingling I found this blog from Microsoft which provides you the attach to download a really cool bit energy that can assist you settle the missing MSIs, or at leastern help you identify them.

See more: Free Tech Answers: How To Resolve Event Id 1505 User Profile Service

I would strongly recommfinish running the energy while you are preparing for organization patching so that you have the right to deal with any problems rather than having to resolve it in the middle of the night.

When you run the energy it will ask you for the installer drive, by default this is c:windowsinstaller it might rerevolve somepoint prefer this:


Hopefully it will rerotate an empty table, however if it does rerevolve information we recognize what to perform to fix it.

You have the right to check out that in the display dump I’ve fixed two lacking msi’s and faibrought about solve 3. However before this does provide us really useful indevelopment. We know what the msi we are missing relates to and the number SQL Server has actually provided to it. SQL Server randomizes the CachedMSIMsp so you can’t just uncover that one.

See more: Different Backgrounds On Each Monitor

Instead what you have to execute to resolve this is search out the package name, sql_is.msi, by the time I’d gained to this point I’d downloaded the variation of SQL Server I was functioning with and also tried a repair which had actually failed. Search for the package name, so looking at the initially one it’s sql_is.msi, copy it to c:windowsinstaller and also rename it to, in our instance, 83717132.msi, repeat this for all absent msi’s and also then you should have the ability to re-run the service load effectively.