The fastest way out of this predicament is to roll your test virtual macihne 
back to the lastest snapshot.

Oh, you're not testing on a VM?  Sorry.

Use orca to modify the custom action table of the MSI that you installed.  Find 
the custom action in the sequence table that you authored it in and modify it 
to have a custom action of "Not Installed".

Next recache the package with the command line:

msiexec /i your.msi REINSTALL=ALL REINSTALLMODE=vomus

You should now be able to uninstall your package.


Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves 
attention? E-Mail Me


--- On Sun, 5/3/09, Ben Axelrod <baxel...@coroware.com> wrote:

> From: Ben Axelrod <baxel...@coroware.com>
> Subject: [WiX-users] help, custom action preventing uninstall
> To: "wix-users@lists.sourceforge.net" <wix-users@lists.sourceforge.net>
> Date: Sunday, May 3, 2009, 3:30 PM
> I created a custom action that runs
> an exe on some of the installed files.  (WiX 3 code
> below).  Now I can't uninstall my product because the
> custom action fails because the files are not found. 
> Does anyone know how I can force the uninstall, or get out
> of this mess some other way?
> 
> How can I prevent this blunder in the future?  I would
> like the custom action to only be run on install.  I
> guess it should also be run on repair, upgrade, and
> reinstall, but only if the files I install exist.  I
> think I heard somewhere that a reinstall is just an
> uninstall then install.  So obviously, my custom action
> should only be run during the install phase...  is
> there some handy condition that I should use?
> 
> Thanks,
> -Ben
> 
> <CustomAction Id="SetEXE"
>              
> Property="MyEXE"
>              
> Value="XCOPY" />
> <CustomAction Id="InvokeEXE"
>              
> Property="MyEXE"
>               Execute
> ="deferred"
>              
> ExeCommand="&quot;SampleFile1.txt&quot;
> C:\Temp"/>
> <UI>
>   <AdminUISequence>
>     <Custom Action="SetEXE"
> After="CostInitialize">1</Custom>
>   </AdminUISequence>
>   <InstallUISequence>
>     <Custom Action="SetEXE"
> After="CostInitialize">1</Custom>
>   </InstallUISequence>
> </UI>
> <AdminExecuteSequence>
>   <Custom Action="SetEXE"
> After="CostInitialize">1</Custom>
>   <Custom Action="InvokeEXE"
> After="InstallFiles">1</Custom>
> </AdminExecuteSequence>
> <InstallExecuteSequence>
>   <Custom Action="SetEXE"
> After="CostInitialize">1</Custom>
>   <Custom Action="InvokeEXE"
> After="InstallFiles">1</Custom>
> </InstallExecuteSequence>
> 
> 
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance
> & Operations 
> Conference from O'Reilly Media. Velocity features a full
> day of 
> expert-led, hands-on workshops and two days of sessions
> from industry 
> leaders in dedicated Performance & Operations tracks.
> Use code vel09scf 
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 


      

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to