Use the dumpbin.exe utility with the /IMPORTS switch on your release custom action dll to see what files it depends on. Check to see if any of those files are missing from the default path of your target machine. If they are, research to see what would be required to statically link to their libraries such that those dlls are no longer required.
-----Original Message----- From: nagaram.c [mailto:nagara...@symphony.cc] Sent: Tuesday, January 06, 2009 9:59 PM To: 'General discussion for Windows Installer XML toolset.'; 'Blair'; ra...@symphony.cc Subject: RE: [WiX-users] getting win32 exception while running the newly added custom ICE The issue still exists for Release build, however works ok with debug build, below is the error log smoke.exe : error SMOK0217 : Error executing ICE action 'ICE900'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this problem. The following string format was not expected by the external UI message logger: "There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ". smoke.exe : error SMOK0217 : Error executing ICE action 'ICE903'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this problem. The following string format was not expected by the external UI message logger: "There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ". - Nag -----Original Message----- From: nagaram.c [mailto:nagara...@symphony.cc] Sent: Wednesday, January 06, 2010 11:30 PM To: 'Blair'; 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] getting win32 exception while running the newlyadded custom ICE This works, Thank you - Nag -----Original Message----- From: Blair [mailto:os...@live.com] Sent: Wednesday, January 06, 2010 10:09 AM To: nagara...@symphony.cc; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] getting win32 exception while running the newly added custom ICE The default build settings for native C++ code generation is to use the runtime DLLs that come with VS2008 (which are NOT resident by default in any OS). For Custom Action use, that isn't the build setting you want. Open the project properties dialog, navigate to Configuration Properties --> C/C++ --> Code Generation, select Debug in the Configuration drop-down at the top of the dialog, change the Runtime Library setting to "Multi-threaded Debug (/MTd)", select Release in the Configuration drop-down at the top of the dialog (approving saving the changes in the confirmation dialog), change the Runtime Library setting to "Multi-threaded (/MT)", then hit Apply and OK. -----Original Message----- From: nagaram.c [mailto:nagara...@symphony.cc] Sent: Wednesday, January 06, 2010 5:17 AM To: 'Blair'; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] getting win32 exception while running the newly added custom ICE Hi, With the release DLL I am getting these below errors, I am using VS2008 for creating this C++ DLL, can you please suggest which of the linker setting I have to select in the project properties dialog for to specify Static Runtime Library setting. smoke.exe : error SMOK0217 : Error executing ICE action 'ICE900'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this problem. The following string format was not expected by the external UI message logger: "There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ". smoke.exe : error SMOK0217 : Error executing ICE action 'ICE903'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this problem. The following string format was not expected by the external UI message logger: "There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. ". Thanks, Nag -----Original Message----- From: Blair [mailto:os...@live.com] Sent: Wednesday, January 06, 2010 4:54 AM To: nagara...@symphony.cc; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] getting win32 exception while running the newly added custom ICE Is it at all possible that the new ICE900 test you wrote uses the C++ runtime DLL? In your C++ build settings you need to make sure you link to the static runtime library AND that you build Release (not Debug) for the version you run away from the developer's box. -----Original Message----- From: nagaram.c [mailto:nagara...@symphony.cc] Sent: Tuesday, January 05, 2010 11:43 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] getting win32 exception while running the newly added custom ICE Hi, I am getting below exception to my newly added ICE, whereas the same works fine in the developer environment but fails in the tester environment, both are XP machines. To the tester environment I have deployed the below files smoke.exe wconsole.dll wix.dll darice.cub (containing the newly added CA DLL) ......... .......... ICE99: Created 06/18/2004. Last Modified 06/18/2004. ICE100: ICE100 - Validates the MsiEmbeddedUI Table, checking for duplicate filenames and validity of order values, attributes, etc. ICE100: Created 04/02/2007. Last Modified 04/02/2007. smoke.exe : error SMOK0216 : An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE900' Fatal error during installation Thanks, Nag ---------------------------------------------------------------------------- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
