On 01-May-12 20:03, Bob Arnson wrote:
> See wix.chm on WIXUI_DONTVALIDATEPATH for how to skip validation.
That sounds perfect Bob. Unfortunately, now when I build from the same
source/toolset, the resulting MSI won't start at all. It gives error 1620 on
WinNT4+SP6 (but works on newer OSes). This happens, of course, with or without
your WIXUI_DONTVALIDATEPATH property. The schema is 200, and when built back in
2010 using the same source and toolset it worked up until the path validation.
Is there anything I can do to determine exactly what caused MSIEXEC 2.00.2600.2
to reject the MSI file? The only ICE I get through Orca is ICE66: "Complete
functionality of the Shortcut table is only available with Windows Installer
version 4.0. Your schema is 200." This is likely caused by the presence of the
(empty) Display* and Description* columns. But I got that in the MSI file built
in 2010 as well.
Here is the short log that is generated by MSIEXEC 2.00.2600.2 on WinNT4+SP6:
=== Verbose logging started: 5/2/12 7:45:13 Build type: SHIP UNICODE
2.00.2600.02 Calling process: C:\WINNT\system32\msiexec.exe ===
MSI (c) (88:6F): Resetting cached policy values
MSI (c) (88:6F): Machine policy value 'Debug' is 0
MSI (c) (88:6F): ******* RunEngine:
******* Product: rmcwin.msi
******* Action:
******* CommandLine: **********
MSI (c) (88:6F): Note: 1: 2203 2: rmcwin.msi 3: -2147286779
MSI (c) (88:6F): MainEngineThread is returning 1620
=== Verbose logging stopped: 5/2/12 7:45:13 ===
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
