Re: [WiX-users] Burn failed to initialize COM at EngineRun().
File the bug. Burn (the engine) should never crash. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Uni Gauldoth [mailto:unigauld...@gmail.com] Sent: Tuesday, May 26, 2015 9:37 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn failed to initialize COM at EngineRun(). Hi, I've found the culprit. I installed a program named Lingoes(a translator), and run the Ligoes.exe in the back. When my installer starts, it loaded the following dll before entering stub.exe's wWinMain. C:\Users\Administrator\AppData\Local\Lingoes\Translator\lingoes-us\OpenText32.dll It looks like this OpenText32.dll already initialized COM using a different thread mode. If I terminate the Ligoes.exe, the problem vanished. Since I'm using debug version of burn.exe, it will crash. In release version of burn.exe, it will not crash because ExitOnFailure is not available under release build. So is this a bug? Or a flaw I can just ignore? Regards, Gauldoth -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn failed to initialize COM at EngineRun().
Hi, I've found the culprit. I installed a program named Lingoes(a translator), and run the Ligoes.exe in the back. When my installer starts, it loaded the following dll before entering stub.exe's wWinMain. C:\Users\Administrator\AppData\Local\Lingoes\Translator\lingoes-us\OpenText32.dll It looks like this OpenText32.dll already initialized COM using a different thread mode. If I terminate the Ligoes.exe, the problem vanished. Since I'm using debug version of burn.exe, it will crash. In release version of burn.exe, it will not crash because ExitOnFailure is not available under release build. So is this a bug? Or a flaw I can just ignore? Regards, Gauldoth On Mon, May 25, 2015 at 5:24 PM, uni unigauld...@gmail.com wrote: Hi, I’m using burn and WPF to write my bundle, the version is v3.9 R2. I’m also using the Prism library. After I wrote a simple UI, I try to run the bundle, and it crashed. I found it crashed in the EngineRun() function. // initialize COM hr = ::CoInitializeEx(NULL, COINIT_MULTITHREADED);//hr equals 0x80010106 - Cannot change thread mode after it is set. // It tried to log the error, but crashed in LogStringWork function because the log is not yet initialized. ExitOnFailure(hr, Failed to initialize COM.); fComInitialized = TRUE; // Initialize dutil. LogInitialize(::GetModuleHandleW(NULL)); fLogInitialized = TRUE; Did I miss something? It looks like someone has already initialized the COM using COINIT_APARTMENTTHREADED. Any help would be appreciated. Regards, Gauldoth -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn failed to initialize COM at EngineRun().
Hi, I'm using burn and WPF to write my bundle, the version is v3.9 R2. I'm also using the Prism library. After I wrote a simple UI, I try to run the bundle, and it crashed. I found it crashed in the EngineRun() function. // initialize COM hr = ::CoInitializeEx(NULL, COINIT_MULTITHREADED);//hr equals 0x80010106 - Cannot change thread mode after it is set. // It tried to log the error, but crashed in LogStringWork function because the log is not yet initialized. ExitOnFailure(hr, Failed to initialize COM.); fComInitialized = TRUE; // Initialize dutil. LogInitialize(::GetModuleHandleW(NULL)); fLogInitialized = TRUE; Did I miss something? It looks like someone has already initialized the COM using COINIT_APARTMENTTHREADED. Any help would be appreciated. Regards, Gauldoth -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
