This appears to affect every installer run via winrm on a w2k8 host --
the install proceeds normally, but the bootstrapper fails to quit when
the process is complete.
I've compiled the bootstrapper and added some debug logging, it looks as
though it gets as far as PostQuitMessage:
[02E4:0B48][2014-09-24T10:35:33]i399: Apply complete, result: 0x0,
restart: None, ba requested restart: No
[02E4:09C0][2014-09-24T10:35:33]i000: process message id 8068, wParam=0,
lParam=d
[02E4:09C0][2014-09-24T10:35:33]i000: WndProc process message id 8068,
wParam=0, lParam=d
[02E4:09C0][2014-09-24T10:35:33]i000: State change to d
[02E4:09C0][2014-09-24T10:35:33]i000: Attempting quiet exit via WM_CLOSE
post to 001A00C2
[02E4:09C0][2014-09-24T10:35:33]i000: process message id 10, wParam=0,
lParam=0
[02E4:09C0][2014-09-24T10:35:33]i000: WndProc process message id 10,
wParam=0, lParam=0
[02E4:09C0][2014-09-24T10:35:33]i000:
CWixStandardBootstrapperApplication::WM_CLOSE
[02E4:09C0][2014-09-24T10:35:33]i000: WndProc process message id 2,
wParam=0, lParam=0
[02E4:09C0][2014-09-24T10:35:33]i000:
CWixStandardBootstrapperApplication::WM_DESTROY -- calling PostQuitMessage
[02E4:09C0][2014-09-24T10:35:33]i000: WndProc process message id 82,
wParam=0, lParam=0
this is where it stops with the installer running, but stuck in the
GetMessage call (verified with windbg).
I'm not really sure what's affecting the behaviour of GetMessage --
AFAICT it ought to wake up and generate a WM_QUIT like normal. Calling
PostQuitMessage multiple times doesn't help, but posting another message
just before the PQM call does, e.g.:
case WM_DESTROY:
BalLog(BOOTSTRAPPER_LOG_LEVEL_STANDARD,
"CWixStandardBootstrapperApplication::WM_DESTROY -- calling
PostQuitMessage");
// saves the day ...
::PostMessage(NULL, WM_USER, 0, 0);
::PostQuitMessage(0);
break;
generates similar output to the above but it actually quits:
[0E50:0D60][2014-09-24T10:48:25]i000: Attempting quiet exit via WM_CLOSE
post to 001B00C2
[0E50:0D60][2014-09-24T10:48:25]i000: process message id 10, wParam=0,
lParam=0
[0E50:0D60][2014-09-24T10:48:25]i000: WndProc process message id 10,
wParam=0, lParam=0
[0E50:0D60][2014-09-24T10:48:25]i000:
CWixStandardBootstrapperApplication::WM_CLOSE
[0E50:0D60][2014-09-24T10:48:25]i000: WndProc process message id 2,
wParam=0, lParam=0
[0E50:0D60][2014-09-24T10:48:25]i000:
CWixStandardBootstrapperApplication::WM_DESTROY -- calling PostQuitMessage
[0E50:0D60][2014-09-24T10:48:25]i000: WndProc process message id 82,
wParam=0, lParam=0
[0E50:0D60][2014-09-24T10:48:25]i000: process message id 400, wParam=0,
lParam=0
[0E50:0D60][2014-09-24T10:48:25]i000: Exit message loop
[0E50:00D4][2014-09-24T10:48:25]i500: Shutting down, exit code: 0x0
All very odd, does anybody have any ideas where I could look next?
Thanks,
Mark
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
