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.
