It's true that most of the time this email list manages to strip attachments.
For those following this thread, here are the pertinent details from the log:
* It is a major upgrade.
* RemoveExistingProducts is scheduled after InstallFinalize.
* The error is being thrown in the product being removed (which is scheduled
right after InstallFinalize).
* REINSTALLMODE does NOT appear to have been explicitly set.
Unfortunately, the log is not a verbose one, so all I have are the action
starts/ends, the final property values for both the nested removal and the
upgrade sessions, and spew from three different custom actions (one of which is
the failing one). I don't have the information on why files/components
were/weren't selected for installation/removal.
>From Dave's description earlier in the thread, the files ended up the same as
>in the earlier product, which still seems strange to me, but without more
>logging I'm still not sure why.
* I would like to know what would happen if you ran Repair right after the
failed successful upgrade.
* I would like to see a comparison of the MsiFileHash table between the two
versions.
* I would like to know if the files were changed at all by anything other than
Windows Installer (even a file system date change).
I would also ask if a failure of RemoveBoxShortcuts is vital. If it isn't, can
you live with that failure not being even reported to the user? If you can,
mark it as return=ignored instead of =check. Also since it is changing machine
state, it (or at least the acting part of it) probably should be deferred
instead of immediate after InstallFinalize.
If you can't make those changes, consider use of the "semi-custom action"
pattern.
Please look at the unversioned file update rules on this page and see if
anything there appears to explain what is happening.
Feel free to send me an updated log that is verbose and I'll share the
analysis. If anyone else wants to see the log he sent me, I'll forward it upon
request only with Dave's permission.
Blair
> From: dsaw...@box.com
> Date: Thu, 8 Aug 2013 11:13:49 -0700
> Subject: Re: [WiX-users] Installation failed, but product updated
> To: os...@live.com
>
> Hi Blair,
> I really appreciate your help! As a piece of good news WiX just beat
> out an incursion from AdvancedInstaller. Box is continuing with WiX to
> make our combined 32/64 bit installer for BoxSync. I attached the complete
> msi log from an install where the product registered but the files didn't
> upgrade. Could the problem be that our files do not have a version
> resource in them? They are python files. I'll post results of your help
> back to the mailing list, but I thought send an attachment might be a
> little much for the list.
>
> Thanks tons!
> -Dave
> ______________________________________
> Dave Sawyer - dsaw...@box.com
> Dogs think they are people. Cats think they are gods.
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
