Discussion:
Windows Installer failed when AppVerifier enabled
(too old to reply)
Jeremy
2008-03-21 07:00:40 UTC
Permalink
Hello,

It's so strangely that my Windows Installer failed to start when msiexec.exe was attached to the AppVerifier and LuaPriv test was enabled. When I tried to start it by typing "msiexec.exe" in the command window it complains: "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application." but it's ok without using AppVerifier.

Here's my environment:
Windows XP sp2
Application Verifier version 3.4
msiexec version 3.1.4000.1823, msi.dll version 3.1.4000.4039

I tried to uninstall/reinstall the windows installer but the problem still exist.

Anyone could give me some info. about it would be appreciate!
Prasad Kakulamarri [MSFT]
2008-03-25 17:54:02 UTC
Permalink
Hi Jeremy,
I could not reproduce the problem you are experiencing. I enabled "LuaPriv"
check on msiexec.exe and I was able to launch it fine.
Can you give me the steps to reproduce? Or attach a debugger to msiexec.exe
and see what DLL is failing to load?

Thanks,
Prasad
Post by Jeremy
Hello,
It's so strangely that my Windows Installer failed to start when msiexec.exe was attached to the AppVerifier and LuaPriv test was enabled. When I tried to start it by typing "msiexec.exe" in the command window it complains: "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application." but it's ok without using AppVerifier.
Windows XP sp2
Application Verifier version 3.4
msiexec version 3.1.4000.1823, msi.dll version 3.1.4000.4039
I tried to uninstall/reinstall the windows installer but the problem still exist.
Anyone could give me some info. about it would be appreciate!
Jeremy
2008-03-26 03:04:26 UTC
Permalink
Hi Prasad,

Yes it seems only happened on my machime. When I tried on another machine the problem doesn't exist so I assume there must be something wrong with the Windows Installer on my machine.

I compared two appverifier logs and found the one generated from my machine only have 4 logEntries with StopCode 0x3304 while the other (the appverifier log generated from the machine doesn't has the problem) has long logEntries except these 4.

Then I use WinDbg to open msiexec and got following info. It stopped at: "ModLoad: 71bf0000 71c03000 C:\WINDOWS\system32\SAMLIB.dll" when the error box pop up.
================================================
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 0xBFC: 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
(bfc.804): Unknown exception - code c0000142 (first chance)
(bfc.804): Unknown exception - code c0000142 (!!! second chance !!!)
eax=0007fc54 ebx=00000000 ecx=0007fc80 edx=7c90eb94 esi=7ffde000 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
======================================================

And here's the log info. generated from the other machime:
======================================================
CommandLine: C:\WINDOWS\system32\msiexec.exe
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
ModLoad: 01000000 01016000 msiexec.exe
ModLoad: 7c900000 7c9b0000 ntdll.dll
AVRF: msiexec.exe: pid 0xF78: flags 0x80000000: application verifier enabled
ModLoad: 5ad10000 5ad56000 C:\WINDOWS\System32\verifier.dll
ModLoad: 00400000 00428000 C:\WINDOWS\System32\vrfcore.dll
ModLoad: 003c0000 003e9000 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...
-- LuaPriv initialized--
ModLoad: 7d1e0000 7d49e000 C:\WINDOWS\system32\msi.dll
(f78.f90): Break instruction exception - code 80000003 (first chance)
eax=003b1ec4 ebx=7ffde000 ecx=00000004 edx=00000010 esi=003b1f98 edi=003b1ec4
eip=7c901230 esp=0007fb20 ebp=0007fc94 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
ntdll!DbgBreakPoint:
7c901230 cc int 3
====================================================================

Jeremy
Post by Prasad Kakulamarri [MSFT]
Hi Jeremy,
I could not reproduce the problem you are experiencing. I enabled "LuaPriv"
check on msiexec.exe and I was able to launch it fine.
Can you give me the steps to reproduce? Or attach a debugger to msiexec.exe
and see what DLL is failing to load?
Thanks,
Prasad
Post by Jeremy
Hello,
It's so strangely that my Windows Installer failed to start when msiexec.exe was attached to the AppVerifier and LuaPriv test was enabled. When I tried to start it by typing "msiexec.exe" in the command window it complains: "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application." but it's ok without using AppVerifier.
Windows XP sp2
Application Verifier version 3.4
msiexec version 3.1.4000.1823, msi.dll version 3.1.4000.4039
I tried to uninstall/reinstall the windows installer but the problem still exist.
Anyone could give me some info. about it would be appreciate!
Jeremy
2008-03-26 05:43:58 UTC
Permalink
And this is only failed when LuaPriv test is enabled, other tests are all fine.
"Jeremy" <***@infor.com.invalid> wrote in message news:***@TK2MSFTNGP05.phx.gbl...
Hi Prasad,

Yes it seems only happened on my machime. When I tried on another machine the problem doesn't exist so I assume there must be something wrong with the Windows Installer on my machine.

I compared two appverifier logs and found the one generated from my machine only have 4 logEntries with StopCode 0x3304 while the other (the appverifier log generated from the machine doesn't has the problem) has long logEntries except these 4.

Then I use WinDbg to open msiexec and got following info. It stopped at: "ModLoad: 71bf0000 71c03000 C:\WINDOWS\system32\SAMLIB.dll" when the error box pop up.
================================================
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 0xBFC: 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
(bfc.804): Unknown exception - code c0000142 (first chance)
(bfc.804): Unknown exception - code c0000142 (!!! second chance !!!)
eax=0007fc54 ebx=00000000 ecx=0007fc80 edx=7c90eb94 esi=7ffde000 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
======================================================

And here's the log info. generated from the other machime:
======================================================
CommandLine: C:\WINDOWS\system32\msiexec.exe
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
ModLoad: 01000000 01016000 msiexec.exe
ModLoad: 7c900000 7c9b0000 ntdll.dll
AVRF: msiexec.exe: pid 0xF78: flags 0x80000000: application verifier enabled
ModLoad: 5ad10000 5ad56000 C:\WINDOWS\System32\verifier.dll
ModLoad: 00400000 00428000 C:\WINDOWS\System32\vrfcore.dll
ModLoad: 003c0000 003e9000 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...
-- LuaPriv initialized--
ModLoad: 7d1e0000 7d49e000 C:\WINDOWS\system32\msi.dll
(f78.f90): Break instruction exception - code 80000003 (first chance)
eax=003b1ec4 ebx=7ffde000 ecx=00000004 edx=00000010 esi=003b1f98 edi=003b1ec4
eip=7c901230 esp=0007fb20 ebp=0007fc94 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
ntdll!DbgBreakPoint:
7c901230 cc int 3
====================================================================

Jeremy
Post by Prasad Kakulamarri [MSFT]
Hi Jeremy,
I could not reproduce the problem you are experiencing. I enabled "LuaPriv"
check on msiexec.exe and I was able to launch it fine.
Can you give me the steps to reproduce? Or attach a debugger to msiexec.exe
and see what DLL is failing to load?
Thanks,
Prasad
Post by Jeremy
Hello,
It's so strangely that my Windows Installer failed to start when msiexec.exe was attached to the AppVerifier and LuaPriv test was enabled. When I tried to start it by typing "msiexec.exe" in the command window it complains: "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application." but it's ok without using AppVerifier.
Windows XP sp2
Application Verifier version 3.4
msiexec version 3.1.4000.1823, msi.dll version 3.1.4000.4039
I tried to uninstall/reinstall the windows installer but the problem still exist.
Anyone could give me some info. about it would be appreciate!
Prasad Kakulamarri [MSFT]
2008-04-01 19:28:01 UTC
Permalink
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
Post by Jeremy
And this is only failed when LuaPriv test is enabled, other tests are all fine.
Hi Prasad,
Yes it seems only happened on my machime. When I tried on another machine the problem doesn't exist so I assume there must be something wrong with the Windows Installer on my machine.
I compared two appverifier logs and found the one generated from my machine only have 4 logEntries with StopCode 0x3304 while the other (the appverifier log generated from the machine doesn't has the problem) has long logEntries except these 4.
Then I use WinDbg to open msiexec and got following info. It stopped at: "ModLoad: 71bf0000 71c03000 C:\WINDOWS\system32\SAMLIB.dll" when the error box pop up.
================================================
CommandLine: C:\WINDOWS\system32\msiexec.exe
Symbol search path is: C:\WINDOWS\Symbols
ModLoad: 01000000 01016000 msiexec.exe
ModLoad: 7c900000 7c9b0000 ntdll.dll
AVRF: msiexec.exe: pid 0xBFC: 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
(bfc.804): Unknown exception - code c0000142 (first chance)
(bfc.804): Unknown exception - code c0000142 (!!! second chance !!!)
eax=0007fc54 ebx=00000000 ecx=0007fc80 edx=7c90eb94 esi=7ffde000 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
7c964ed1 c9 leave
======================================================
======================================================
CommandLine: C:\WINDOWS\system32\msiexec.exe
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
ModLoad: 01000000 01016000 msiexec.exe
ModLoad: 7c900000 7c9b0000 ntdll.dll
AVRF: msiexec.exe: pid 0xF78: flags 0x80000000: application verifier enabled
ModLoad: 5ad10000 5ad56000 C:\WINDOWS\System32\verifier.dll
ModLoad: 00400000 00428000 C:\WINDOWS\System32\vrfcore.dll
ModLoad: 003c0000 003e9000 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...
-- LuaPriv initialized--
ModLoad: 7d1e0000 7d49e000 C:\WINDOWS\system32\msi.dll
(f78.f90): Break instruction exception - code 80000003 (first chance)
eax=003b1ec4 ebx=7ffde000 ecx=00000004 edx=00000010 esi=003b1f98 edi=003b1ec4
eip=7c901230 esp=0007fb20 ebp=0007fc94 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
7c901230 cc int 3
====================================================================
Jeremy
Post by Prasad Kakulamarri [MSFT]
Hi Jeremy,
I could not reproduce the problem you are experiencing. I enabled "LuaPriv"
check on msiexec.exe and I was able to launch it fine.
Can you give me the steps to reproduce? Or attach a debugger to msiexec.exe
and see what DLL is failing to load?
Thanks,
Prasad
Post by Jeremy
Hello,
It's so strangely that my Windows Installer failed to start when msiexec.exe was attached to the AppVerifier and LuaPriv test was enabled. When I tried to start it by typing "msiexec.exe" in the command window it complains: "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application." but it's ok without using AppVerifier.
Windows XP sp2
Application Verifier version 3.4
msiexec version 3.1.4000.1823, msi.dll version 3.1.4000.4039
I tried to uninstall/reinstall the windows installer but the problem still exist.
Anyone could give me some info. about it would be appreciate!
Jeremy
2008-04-02 03:53:48 UTC
Permalink
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
Post by Prasad Kakulamarri [MSFT]
Hi Jeremy,
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.
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
Jeremy
2008-04-02 16:42:01 UTC
Permalink
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 -:)
Phil Wilson
2008-04-02 18:55:25 UTC
Permalink
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]
Post by Jeremy
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 -:)
Jeremy
2008-04-03 01:49:59 UTC
Permalink
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
Post by Phil Wilson
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]
Post by Jeremy
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 -:)
Loading...