Local cached package 'C:\WINDOWS\Installer\xxxxxx.msi' is missing.

Evern seen the error the in the client.msi.log file that a local package is missing when trying to install the client.  This could be because a dependence has been removed or badly corrupted, but what file is missing?

Looking in the client.msi.log you might see this line:

MSI (s) (D0:F4) [17:45:28:546]: Warning: Local cached package 'C:\WINDOWS\Installer\6363739.msi' is missing.

Ccmsetup.log:

An MP does not exist on this machine.
Failed with error code 0x8007064c.
Installing version 4.00.6487.2700 of the client with product code {CAE5379F-5C3D-4D0D-AA57-DC1134125BA5}
MSI PROPERTIES are  .....................
IsFileMicrosoftTrusted Verified file 'C:\Windows\ccmsetup\{18173E5E-0E79-4447-A4DC-2CEEAA239871}\client.msi' is MS signed.
Installation failed with error code 1612

Client.msi.log

MSI (s) (84:78) [14:53:58:896]: ******* RunEngine:
           ******* Product: C:\Windows\ccmsetup\{18173E5E-0E79-4447-A4DC-2CEEAA239871}\client.msi
           ******* Action:
           ******* CommandLine: **********

MSI (s) (84:78) [14:53:58:927]: Warning: Local cached package 'C:\Windows\Installer\723298.msi' is missing.
MSI (s) (84:78) [14:53:58:927]: SOURCEMGMT: Looking for sourcelist for product {CAE5379F-5C3D-4D0D-AA57-DC1134125BA5}
MSI (s) (84:78) [14:53:58:942]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (84:78) [14:53:58:942]: SOURCEMGMT: Failed to resolve source



Solution:
these all point to a possible missing file.  Indeed if you look in the installer folder you will be missing a file.  The problem is that these files are random and you can't just look up the file on another machine. 

So how do you find what you need?

for ConfigMgr 2007 you can look here
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\F9735EACD3C5D0D4AA75CD114321B55A

But the best thing is to stop at the Products node

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\

and search the entire node to look up the XXXx.msi you are missing to see which product is missing.  From there you can then go to another machine and copy the XXXX.msi to the broken machine.

You must look at the InstalledProperties\LocalPackage to see the file name
C:\Windows\Installer\129227f.msi

From here you can either rename the msi file or modify the key to match the file name.

Next restart your install, is this a supported method.  No but it should work.  With all unsupported process, please use at your own risk and test in a lab enviroment first.

Right click Tool: Status Messages

This will work for both SMS or SCCM. This is a neat trick. We will use the status message viewer from Microsoft to look at a computer but with a right click. No longer do you need to run through the MMC.

<ActionGroups>
<actiondescription class="Executable" displayname="Status Messages" mnemonicdisplayname="Status Messages" description="Display machine status messages">
</executable> <filepath>D:\Program Files\Microsoft Configuration Manager\AdminUI\bin\i386\statusmessages.exe <parameters>##SUB:Name## </actiongroups>

D:\Program Files\Microsoft Configuration Manager\AdminUI\XmlStorage\Extensions\Actions\7ba8bf44-2344-4035-bdb4-16630291dcf6\Tools.xml

This needs to go into your XML file in the previous folder. Please consult the MS documentation. This is only the inset not the whole file. You will need to change the location of the file path to C, E, or whatever your drive it.

To make this work in SMS see my section on SMS tools and the MMC registry. You only need to add the path and sub:netbiosname to the script. Now you can right click on a client and get the status messages very easily now. Be aware that this will pull in ALL messages so you will need to click stop or you will be there all day.

If the application has problem the first time you run it then you need to just double click on StatusMessages.exe and type in your server name and ok. Then the tool will work correctly the next time for you.

[Update June 2009]
Well I created this back in 2005 when I first started working with SMS. Well Robert Mitsch has an update which I think is great

The changes are as follows
<FilePath>C:\xxxxxxx\AdminUI\bin\i386\statview.exe</FilePath>
<Parameters>/SMS:Server=\\##SUB:__Server## /SMS:Path=##SUB:__Namespace## /SMS:System=##SUB:Name##</Parameters>

update blog entry: http://sms-hints-tricks.blogspot.com/2009/06/right-click-status-messages.html

Lock down SMS Control Panel

There are several ways to lock down the control panel I will address the one I know or found. Since this has come up in other forums and newsgroups I thought I would add my 2 cents.
Why would you want to lock it down. Well, if you have a user that is an admin on their machine they might revolt and turn off the service or fool around with the cache to prevent SMS from doing its job. It is a fact of life that some users will have admin rights to their machine. This will hopefully deter or slow them down. There isn't a way to totally stop them.

1. Hide the SMS Control Panel for current user (Systems Managment)
This will require a restart, force it or just wait for them to restart.
-------no show.reg------------------
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Control Panel\don't load]
"SMSCFGRC.cpl"="No"
---------------------------------------------
2. Disable sections of the Contol Panel [Courtesy of Rune Norberg, MS Newsgroup]
For site assignment:>
HKLM\Software\Microsoft\SMS\Mobile Client\Configuration\CP Site Assignment> Options=Disabled (REG_SZ)
For cache:>
HKLM\Software\Microsoft\SMS\Mobile Client\Configuration\CP Cache> Options=Disabled (REG_SZ)
----------------------------------

3. Restart CCM Service on remote machine
If the admin keeps turning off the service you can setup a scheduled task to run say every 3 hours to turn it back on. If they turn off WMI then you have a problem but you can use this to give you a return value if it is failing to start it.

-------------restart sms agent.vbs------------
strComputer = "YourComputer"
strCommand = "net start ccmexec"
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" _
& strComputer & "\root\cimv2")


Set oStartup = objWMIService.Get("Win32_ProcessStartup")
Set objConfig = oStartup.SpawnInstance_
objConfig.ShowWindow = 1

Set oProcess = objWMIService.Get("Win32_Process")
intReturn = oProcess.Create (strCommand, Null, objConfig, intProcessID)
‘’use the intReturn if you want to log success or failure, maybe they turned off Dcom or WMI
--------------------------------------


None of these are top secret and it will only take a little bit of digging for them to fix it. But it will deter some people. You can only try so much.