2 replies to this topic

[mgsram]

On a Windows XP SP2 PC, for one of our internal applications, the Self Repair window pops up unexpectedly. It happens consistently the first time the application is launched and then onwards, it happens randomly.

The Event Log only has an Event ID 1001 as shown below.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 3/4/2008
Time: 2:47:50 PM
User: INLAB\ap002
Computer: DDW7WW71
Description:
Detection of product '{F13444D1-5725-40CB-9066-F791DF214291}', feature 'ObjectModels' failed during request for component '{90EE7875-8ACB-11D6-9E9A-000255345589}'

I verifed that the keypath is set correctly. I did that by directly looking at the tables. To double check that the MSI does not hav a corrupt keypath, I used "Orca" that comes with Windows Installer SDK Tools. It looked fine.

Also I ran through ICE validations and even with that, i did not find any issues.

Finally, I turned Windows Installer logging ON. That did not help either as it did not have any entry that should point out WHY the self repair was triggered. It only had entries that captured what happened as part of the self repair.

Has anyone here seen this kind of behavior ? Am I missing something? Do you have any other pointers I should check?

[mgsram]

I ran the application through WinDbg and I got some additional hint. Here is an excerpt of the WinDbg output window.

===================================================
MSI © (D8:84) [10:46:24:017]: Entering MsiProvideComponentFromDescriptor. Descriptor: eaLTv[7,o8SP_vVR8AcVObjectModels>@GGYVgqBg(dcd_!7Ik.T, PathBuf: 1549F874, pcchPathBuf: 1549F870, pcchArgsOffset: 1549F7D0
MSI © (D8:84) [10:46:24:033]: MsiProvideComponentFromDescriptor is returning: 0
MSI © (D8:84) [10:46:24:033]: Entering MsiProvideComponentFromDescriptor. Descriptor: eaLTv[7,o8SP_vVR8AcVObjectModels>@GGYVgqBg(dcd_!7Ik.T, PathBuf: 1549EB68, pcchPathBuf: 1549EB64, pcchArgsOffset: 1549EAC4
MSI © (D8:84) [10:46:24:033]: Detection of product '{F13444D1-5725-40CB-9066-F791DF214291}', feature 'ObjectModels' failed during request for component '{90EE7875-8ACB-11D6-9E9A-000255345589}'

MSI © (D8:84) [10:46:24:048]: Entering MsiConfigureFeature. Product: {F13444D1-5725-40CB-9066-F791DF214291}, Feature: ObjectModels, Installstate: 5
MSI © (D8:84) [10:46:24:048]: Machine policy value 'Timeout' is 1800
MSI © (D8:84) [10:46:24:064]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI © (D8:84) [10:46:24:064]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI © (D8:84) [10:46:24:095]: Policy value 'Logging' is 'voicewarmup'
ModLoad: 76bb0000 76bb5000 C:\WINDOWS\system32\SFC.DLL
ModLoad: 76c60000 76c8a000 C:\WINDOWS\system32\sfc_os.dll
ModLoad: 76c30000 76c5e000 C:\WINDOWS\system32\WINTRUST.dll
ModLoad: 77a80000 77b14000 C:\WINDOWS\system32\CRYPT32.dll
ModLoad: 77b20000 77b32000 C:\WINDOWS\system32\MSASN1.dll
ModLoad: 76c90000 76cb8000 C:\WINDOWS\system32\IMAGEHLP.dll
MSI © (D8:18) [10:46:24:111]: Resetting cached policy values
MSI © (D8:18) [10:46:24:111]: Machine policy value 'Debug' is 7
MSI © (D8:18) [10:46:24:111]: ******* RunEngine:
******* Product: {F13444D1-5725-40CB-9066-F791DF214291}
******* Action:
******* CommandLine: ADDDEFAULT=ObjectModels
MSI © (D8:18) [10:46:24:126]: Client-side and UI is none or basic: Running entire install on the server.
MSI © (D8:18) [10:46:24:126]: Grabbed execution mutex.
MSI © (D8:18) [10:46:24:142]: Cloaking enabled.
MSI © (D8:18) [10:46:24:142]: Attempting to enable all disabled priveleges before calling Install on Server
MSI © (D8:18) [10:46:24:173]: Incrementing counter to disable shutdown. Counter after increment: 0

=====================================================

In the complete log, there are several calls to MsiProvideComponentFromDescriptor and except the one above, all of them are returning 0. Obviously MsiProvideComponentFromDescriptor is failing. Any information on what it does and why it may fail would certainly be helpful.

[Stefan Krueger]

Apparently, Windows Installer thinks that the component with ComponentId {90EE7875-8ACB-11D6-9E9A-000255345589} in feature ObjectModels is broken. Did you double check the key path of this component? What is it (file or registry) and where? Is it available to the user starting the application (think permissions, network paths, drive mappings, user context switching caused by UAC, etc.)