Wix is allowing me to create msi files with a large number in the fourth
version index (6-digit numbers, i.e. 111111).

I'm trying to use burn to create a bootstrapper which bundles my wix
installer. When I include an msi in the bundle which has a fourth version
index greater than 65535 (16-bit unsigned) I get MSI parsing errors when
executing the bootstrapper. No error pop-up is displayed, the only
indication of the parsing error in in the Setup log file. Parsing errors in
the Setup log file appear as follows:

[25C4:25D0][2014-06-09T14:24:10]i001: Burn v3.8.1128.0, Windows v6.3 (Build
9600: Service Pack 0), path: C:\Users\ejcarpen\Documents\Visual Studio
2010\Projects\Bootstrapper1\Bootstrapper1\bin\Debug\Bootstrapper1.exe,
cmdline: ''
[25C4:25D0][2014-06-09T14:24:10]e000: Error 0x8002000a: Failed to parse
@Version: 1.0.0.65536
[25C4:25D0][2014-06-09T14:24:10]e000: Error 0x8002000a: Failed to parse MSI
package.
[25C4:25D0][2014-06-09T14:24:10]e000: Error 0x8002000a: Failed to parse
packages.
[25C4:25D0][2014-06-09T14:24:10]e000: Error 0x8002000a: Failed to load
manifest.
[25C4:25D0][2014-06-09T14:24:10]e000: Error 0x8002000a: Failed to
initialize core.

This is reproducible by building an empty setup project with version
1.0.0.65536 and adding it to an empty bootstrapper project

Is there a way around this issue? Is it a bug or expected behavior based on
MS version handling limitations? I find it strange that wix allows me to
build MSI files that the wix bootstrapper can't parse

Thanks,
-- 
-Ed
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to