Have you considered using the <iis:Certificate> (and related) elements instead of your own custom action? These will likely have fewer bugs (lower chance of setup failure) than a custom-coded solution, as well as handle repair, uninstall, patching, etc. correctly.
Part of the philosophy underlying wix's design is that users should only write declarative authoring to represent the things they want installed, and let the installation engine (and/or the built-in wix custom actions) handle the actual installation for you. Thanks, Mike Carlson -----Original Message----- From: phillip_sid...@dellteam.com [mailto:phillip_sid...@dellteam.com] Sent: Thursday, January 07, 2010 1:10 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] unexplained Custom Action failure I setup a Custom Action to call a simple command line utility I created that installs an SSL certificate. It keeps failing so I took the contents of the log file that have the Custom Action arguments and execute them manually in a command window. Of course, the certificate installs correctly. I even changed the account running the MSI to run as me so I could eliminate any security/credentials issues and I get the same result; it fails when running from the MSI and succeeds when running as me. I then loaded up SysInternals procmon to compare the execution of this command line utility in each scenario. All of the procmon parameters are identical!! This includes command line args, user account executing the process and bitness of the process. Note that the installer is running on Windows Server 2008 VM server and in each case the command line is running a 64 bit process. Here are the .wxs snippets for the custom action, and the resulting command line: <CustomAction Id="Set_InstallDITDaoSslCertificateArgs" Property="InstallDITDaoSslCertificateArgs" Value="/ce:add /cf:"[UTILITYPATH]UsSslCert.pfx" /cpwd:[SSLCERTPWD] /cs:my /cl:localmachine /cid:"[SSLCERTID]"" Execute="immediate" /> <CustomAction Id="InstallDITDaoSslCertificateToPersonal" Directory="UTILITYPATH" ExeCommand=""[UTILITYPATH]InstallUtil.exe" [InstallDITDaoSslCertificateArgs]" Execute="immediate" Return="ignore" /> "c:\RevProxy\Install\DAO\InstallUtil\InstallUtil.exe" /ce:add /cf:"c:\RevProxy\Install\DAO\InstallUtil\UsSslCert.pfx" /cpwd:ABB66C32-D9F9-6c9a-81C7-C998FF444C32 /cs:my /cl:localmachine /cid:" AbzJc2FFmQeHJGAZrgU9bAjMGbX=" Of course, I have changed the sensitive data to protect the innocent... Any idea why this could be failing inside the MSI? I am pulling my hair out at this point. Thanks. - Phil ------------------------------------------------------------------------------ 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
