I'm getting an error PYRO0130 in the table MsiAssemblyName which makes no sense to me, especially since the wixmst file entry for that doesn't seem to match the error message (at least to my mind). Why would modifying a field on a row (when the field is not part of the primary key) generate this error, especially since there are no rows being added?
Here is the error message: error PYRO0130 : The primary key 'PlatformApi_Interop_Comp/version' is duplicated in table 'MsiAssemblyName'. Please remove one of the entries or rename a part of the primary key to avoid the collision. And here is the portion from the wixmst for the entire table: <table name="MsiAssemblyName" xmlns="http://schemas.microsoft.com/wix/2006/objects";> - <row sectionId="/wix.section.2" sourceLineNumber="e:\enlistments\wlx\main-2\client\contact\setup\msm\ContactMSM.wxs*276"> <field>PlatformApi_Interop_Comp</field> <field>culture</field> <field>neutral</field> </row> - <row sectionId="/wix.section.2" sourceLineNumber="e:\enlistments\wlx\main-2\client\contact\setup\msm\ContactMSM.wxs*276"> <field>PlatformApi_Interop_Comp</field> <field>name</field> <field>LivePlatform.Interop</field> </row> - <row sectionId="/wix.section.2" sourceLineNumber="e:\enlistments\wlx\main-2\client\contact\setup\msm\ContactMSM.wxs*276"> <field>PlatformApi_Interop_Comp</field> <field>processorArchitecture</field> <field>MSIL</field> </row> - <row sectionId="/wix.section.2" sourceLineNumber="e:\enlistments\wlx\main-2\client\contact\setup\msm\ContactMSM.wxs*276"> <field>PlatformApi_Interop_Comp</field> <field>publicKeyToken</field> <field>8416CC26C44011B1</field> </row> - <row op="modify" sectionId="/wix.section.2" sourceLineNumber="e:\enlistments\wlx\main-2\client\contact\setup\msm\ContactMSM.wxs*276"> <field>PlatformApi_Interop_Comp</field> <field>version</field> <field modified="yes">15.0.2300.501</field> </row> </table> As you can see, the only operation on that table is to modify just one row, the one that "now has a duplicate". However, neither the target wixpdb (or msi) nor the upgrade wixpdb (or msi) contain any other rows (each contains just those five rows). Any ideas? A search of the wix-users mail-list showed just one other possible hit for this issue, an unresolved (on the list) mail from INRO(Robert Inzinger) <robert.inzin...@skidata.com> from Wed, 29 Oct 2008 14:52:48 +0100 titled "[WiX-users] Pyro and .Net Assemblies" (which looks to me to probably be the same issue). ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
