Bugs item #1807128, was opened at 2007-10-03 12:24 Message generated for change (Comment added) made by robmen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1807128&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: light >Group: v3.0 >Status: Closed Resolution: Accepted Priority: 5 Private: No Submitted By: Martin Lavelle (hypercaust) >Assigned to: Rob Mensching (robmen) Summary: Some Feature Colums to small Initial Comment: Using Release 3.0.3307.0, I get the following ICE32 Errors: ICE32: Created 07/30/98. Last Modified 10/08/98. C:\TEMP\u0hywyrl\Test.msi : error LGHT0204 : ICE32: Possible Mis-Aligned Foreign Keys Feature.1 = s38 Condition.Feature_ = s32 ICE32: ODBCDataSource table is not in database, but is listed in the _Validation table as a foreign key of Component.KeyPath C:\TEMP\u0hywyrl\Test.msi : error LGHT0204 : ICE32: Possible Mis-Aligned Foreign Keys Feature.1 = s38 PublishComponent.Feature_ = s32 ICE32: Differences found = TRUE ---------------------------------------------------------------------- >Comment By: Rob Mensching (robmen) Date: 2008-05-02 03:24 Message: Logged In: YES user_id=991639 Originator: NO Blank tables are added by the WiX toolset only when absolutely necessary (i.e. the package won't instal if they aren't there). The EnsureTable is the work around to get the correct schema into the MSI before a poorly authored Merge Module gets in and messes things up. ---------------------------------------------------------------------- Comment By: Andrew Sampson (malesh) Date: 2007-11-17 22:05 Message: Logged In: YES user_id=1939857 Originator: NO Ran into this problem myself: it was microsoft's vfpoledb.msm which caused the problem. Obviously an old schema - the Feature keys in various tables were s32 instead of s38. The problem can be worked around by using <EnsureTable> for the particular tables that have bad keys - then WiX seems to output tables with the correct schema. It seems like the proper fix should be for WiX to not output blank tables? ---------------------------------------------------------------------- Comment By: Martin Lavelle (hypercaust) Date: 2007-10-19 06:09 Message: Logged In: YES user_id=1322672 Originator: YES Yes, it was a Microsoft Merge Module or two that was screwing up the schema. Very astute of you to ask. Apologies for wasting your time. I suppose I'll have to remake them :( ---------------------------------------------------------------------- Comment By: pmarcu (pmarcu) Date: 2007-10-09 15:22 Message: Logged In: YES user_id=1612676 Originator: NO The table definitions look correct in WiX and I'm not able to repro this ice error using msi's build only with WiX. Is there an MSM in the equation here? ---------------------------------------------------------------------- Comment By: pmarcu (pmarcu) Date: 2007-10-08 10:01 Message: Logged In: YES user_id=1612676 Originator: NO Can you provide the steps to reproduce this? Possibly your test msi to start and the wix authoring that produced it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1807128&group_id=105970 ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
