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: Open Resolution: None Priority: 5 Private: No Submitted By: david (dextersinister) Assigned to: sameer garde (sameerg) 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-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 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
