Re: Windows Installer failed when AppVerifier enabled

Hi Prasad,

Thanks for your instruction. Not sure I correctly followed your steps but I opened msiexec.exe from WinDbg by selecting "Open Executable..." under File menu with loader snaps enabled and got the following debug spew:
------------------------------------------------------------------------------
CommandLine: C:\WINDOWS\system32\msiexec.exe
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
ModLoad: 01000000 01016000 msiexec.exe
ModLoad: 7c900000 7c9b0000 ntdll.dll
AVRF: msiexec.exe: pid 0xEB4: flags 0x80000000: application verifier enabled
ModLoad: 5ad10000 5ad56000 C:\WINDOWS\System32\verifier.dll
ModLoad: 00400000 00428000 C:\WINDOWS\System32\vrfcore.dll
ModLoad: 003d0000 003f9000 C:\WINDOWS\System32\vfluapriv.dll
ModLoad: 77c10000 77c68000 C:\WINDOWS\system32\msvcrt.dll
ModLoad: 7c800000 7c8f5000 C:\WINDOWS\system32\KERNEL32.dll
ModLoad: 77dd0000 77e6b000 C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 77e70000 77f02000 C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 77fe0000 77ff1000 C:\WINDOWS\system32\Secur32.dll
ModLoad: 76bf0000 76bfb000 C:\WINDOWS\System32\PSAPI.DLL
ModLoad: 774e0000 7761d000 C:\WINDOWS\system32\ole32.dll
ModLoad: 77f10000 77f57000 C:\WINDOWS\system32\GDI32.dll
ModLoad: 7e410000 7e4a0000 C:\WINDOWS\system32\USER32.dll
AVRF: verifier.dll provider initialized for msiexec.exe with flags 0x80000000
ModLoad: 76390000 763ad000 C:\WINDOWS\system32\IMM32.DLL
ModLoad: 629c0000 629c9000 C:\WINDOWS\system32\LPK.DLL
ModLoad: 74d90000 74dfb000 C:\WINDOWS\system32\USP10.dll
LuaPriv: Attaching to process...
ModLoad: 0a000000 0a012000 C:\WINDOWS\system32\EntApi.dll
ModLoad: 5b860000 5b8b4000 C:\WINDOWS\system32\NETAPI32.dll
-- LuaPriv initialized--
ModLoad: 77690000 776b1000 C:\WINDOWS\system32\NTMARTA.DLL
ModLoad: 76f60000 76f8c000 C:\WINDOWS\system32\WLDAP32.dll
ModLoad: 71bf0000 71c03000 C:\WINDOWS\system32\SAMLIB.dll
(eb4.93c): Unknown exception - code c0000142 (first chance)
(eb4.93c): Unknown exception - code c0000142 (!!! second chance !!!)
eax=0007fc54 ebx=00000000 ecx=0007fc80 edx=7c90eb94 esi=7ffd5000 edi=c0000142
eip=7c964ed1 esp=0007fc54 ebp=0007fca4 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
ntdll!RtlRaiseStatus+0x26:
7c964ed1 c9 leave
0:000> kb
ChildEBP RetAddr Args to Child
0007fca4 7c93f8fb c0000142 0007fd30 0000005c ntdll!RtlRaiseStatus+0x26
0007fd1c 7c90eac7 0007fd30 7c900000 00000000 ntdll!_LdrpInitialize+0x241
00000000 00000000 00000000 00000000 00000000 ntdll!KiUserApcDispatcher+0x7
------------------------------------------------------------------------------------

The debug stopped at line "ModLoad: 71bf0000 71c03000 C:\WINDOWS\system32\SAMLIB.dll" when the error dialog pops up and so I closed the dialog and then type kb.

Jeremy

"Prasad Kakulamarri [MSFT]" <PrasadKakulamarriMSFT@discussions.microsoft.com > wrote in message news:9D1C6919-9CB8-4181-AE37-EB24C132B150@microsoft.com...
> Hi Jeremy,
> In order to identify what dll is failing to load, please follow the steps below:
> 1) Enable loader snaps: run gflags.exe that is available in the debugger
> package, go to the "Image File" tab, enter "msiexec.exe" in the text box and
> click on the Tab button on the keyboard.
> check the check box that says "Show loader snaps", Click OK and close
> gflags.exe window.

> 2) Launch msiexec.exe under a debugger. It will now show a lot of debug spew

> 3) When you hit the failure, yype KB at the debugger prompt to get that
> callstack.

> 4) Copy the entire debug spew from the beginning and post it here.
>
> To disable loader snaps:
> Launch gflags.exe, go to "Image File" tab, type msiexec.exe and click on tab
> button.
> Uncheck the "Show loader snaps" check box.
>
> Thanks,
> Prasad

This is the first time I was using WinDbg (never touched it before) so not
sure I correctly followed your instruction. Please figure out if there's
anything wrong, thanks -

Attaching to msiexec.exe is likely to be dodgy. A typical installation can
involve three, one is the service executable for the MsiServer service,
another will be the user mode executable fired up to do the UI part of your
install (the service does the rest) and others are launched to run
impersonated custom actions. Which one do you think you need? What are you
verifying? An install?
--
Phil Wilson
[MVP Windows Installer]

"Jeremy" <Jeremy@discussions.microsoft.com> wrote in message
news:BCD8A0ED-4F39-4052-AE7F-6C7E2AC4C362@microsoft.com...
> This is the first time I was using WinDbg (never touched it before) so not
> sure I correctly followed your instruction. Please figure out if there's
> anything wrong, thanks -

Hi Phil,

This is the Vista logo test requirement to attach msiexec.exe and application install executable to AppVerifier so the install should be verifying.

Jeremy

"Phil Wilson" <phil.wilson@wonderware.something.com> wrote in message news:OZBldMPlIHA.5820@TK2MSFTNGP04.phx.gbl...
> Attaching to msiexec.exe is likely to be dodgy. A typical installation can
> involve three, one is the service executable for the MsiServer service,
> another will be the user mode executable fired up to do the UI part of your
> install (the service does the rest) and others are launched to run
> impersonated custom actions. Which one do you think you need? What are you
> verifying? An install?
> --
> Phil Wilson
> [MVP Windows Installer]
>
> "Jeremy" <Jeremy@discussions.microsoft.com> wrote in message
> news:BCD8A0ED-4F39-4052-AE7F-6C7E2AC4C362@microsoft.com...
>> This is the first time I was using WinDbg (never touched it before) so not
>> sure I correctly followed your instruction. Please figure out if there's
>> anything wrong, thanks -
>
>