Bugs item #1911165, was opened at 2008-03-10 08:39 Message generated for change (Comment added) made by dextersinister You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1911165&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: v2.0 Status: Closed Resolution: Rejected Priority: 5 Private: No Submitted By: david (dextersinister) Assigned to: Rob Mensching (robmen) Summary: Light fails while adding merge module Initial Comment: Log output: Updating file information. Generating database. Merging modules. light.exe : error LGHT0001 : Error HRESULT E_FAIL has been returned from a call to a COM component. Exception Type: System.Runtime.InteropServices.COMException Stack Trace: at Microsoft.Tools.WindowsInstallerXml.IMsmMerge2.Merge(String feature, String directory) at Microsoft.Tools.WindowsInstallerXml.Binder.MergeModules(String databasePath, Output output) in c:\WiXbuilds\v2.0.5805.0.dmm\src\wix\Binder.cs:line 1432 at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output) in c:\WiXbuilds\v2.0.5805.0.dmm\src\wix\Binder.cs:line 390 at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) in c:\WiXbuilds\v2.0.5805.0.dmm\src\light\light.cs:line 467 ********** Tested with v2.0.5805.0 using older version of mergemod.dll [from v2.0.5213.0 release], compiled without error ... also tested with mergemod.dll from v3.0.3829.0 release, compiled without error. Attempted to attach merge module for testing ... but it's too large [340k] ... will email if desired. ---------------------------------------------------------------------- >Comment By: david (dextersinister) Date: 2008-05-15 09:00 Message: Logged In: YES user_id=1376583 Originator: YES Hi Rob - Sorry to be a pain, but this doesn't answer [at least to me, but I will confess to not being an expert here ... and throw myself on the mercy of the court <grin>] why the same failure occurs with VC_User_CRT71_RTL_X86_---.msm, or why simply deleting the Shortcut table 'fixed' the problem ... I agree wholeheartedly that the CrystalReports merge modules are a nightmare ... but some of us are getting the same type of failure(s) in merge modules from other vendors [as in the case of the VC_User_CRT71_RTL_X86_---.msm module] or from modules which have been built in-house ... If you'd like to take a look at one of my modules that causes this failure, please let know where/how to send it to you ... it's too large to attach here ... I'm also not clear on why simply changing to an older version of mergemod.dll would also 'fix' the issue ... again, I'm not an expert ... but it looks to me like the new(er) version(s) of mergemod.dll are passing back something that WiX doesn't digest properly since the failing code hasn't changed [as far as I can tell] between the v2.0.5213.0 release and the 2 later versions ... Thanks for your patience with this non-expert. Best regards, -dmm ---------------------------------------------------------------------- Comment By: Rob Mensching (robmen) Date: 2008-05-14 22:41 Message: Logged In: YES user_id=991639 Originator: NO The problem is that the Merge Module you are merging in is invalid. The PIDKEY property is not properly modularized and is colliding with an existing property in your MSI. You need to fix the Merge Module (or have the author fix it if you didn't create it). The error message could be better in WiX v2 but we're not going to an invasive change like that at this time. ---------------------------------------------------------------------- Comment By: david (dextersinister) Date: 2008-05-06 08:12 Message: Logged In: YES user_id=1376583 Originator: YES Here's the merge log ... Using WiX v2.0.5805.0 with mergemod.dll v4.0.6000.16384 [as supplied in binaries archive]. Light log shows same failure(s) as originally described. Thanks, -dmm File Added: mergeLog.zip ---------------------------------------------------------------------- Comment By: Bob Arnson (barnson) Date: 2008-05-05 21:05 Message: Logged In: YES user_id=26581 Originator: NO Please attach merge.log. ---------------------------------------------------------------------- Comment By: david (dextersinister) Date: 2008-05-05 13:18 Message: Logged In: YES user_id=1376583 Originator: YES Per Bob's suggestion, I ran a test with the -notidy switch ... and reviewed the merge.log file from a failing LIGHT run. The log shows these lines as the last entries: Merging Table: Shortcut Closed Merge Module. > Warning: Changes were not saved to MSI Database. Closed MSI Database. Subsequent testing using the same merge modules [but dropping the empty Shortcut tables] worked properly ... What is odd is that there are numerous errors shown in the log before the warning, and these did not cause the run to fail ... I can provide more info if needed ... Thanks, -dmm ---------------------------------------------------------------------- Comment By: Bob Arnson (barnson) Date: 2008-05-03 11:27 Message: Logged In: YES user_id=26581 Originator: NO Try building with light's -notidy switch to save merge.log, which should contain extra details about the actual error. ---------------------------------------------------------------------- Comment By: Jaap de Wolff (de-wolff) Date: 2008-03-31 04:53 Message: Logged In: YES user_id=238263 Originator: NO VC_User_CRT71_RTL_X86_---.msm is one of the msm's with can cause this error. This msm is delivered with Visual Studio .NET 2003. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1911165&group_id=105970 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
