I'm seeing the following weirdness in the setup log on some of our clients' machines:
MSI (s) (74:88) [16:20:20:178]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIC1F3.tmp, Entrypoint: SaveOldConfig Action start 16:20:20: CA_SaveOldConfig. SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSIC1F3.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action migrateconfig!Migration.MigrateCustomAction.SaveOldConfig SaveOldConfig: Save successful. CustomAction CA_SaveOldConfig returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 16:20:20: CA_SaveOldConfig. Return value 3. Note that CA succeeded and returned ActionResult.Success. However, the CA still failed with 1603. Is this something SfxCa.cpp or in the wrapper CustomActionProxy that might have returned the 1603? Note that the CA runs in immediate mode and this error happens on a small number of machines. This seems related to http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-Custom-Act ion-fails-intermittently-on-some-machines-td4659699.html. Was that issue resolved? Also I think we are only using the 32-bit sfxca and deploying it on both 64 and 32 bit machines. Could this be causing this problem? Any help would be greatly appreciated. Thanks! Bassam ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
