On 8/4/2010 7:39 PM, Blair wrote:
>> From the install log you sent the link to earlier:
>
> What is standing out to me (from the properties, this is (I'm assuming)
> installing 0.5.0 over 0.3.0 via major upgrade):
>
> Before the sequence table is parsed:
>
> MSI (s) (78:4C) [20:14:06:466]: Product not registered: beginning first-time
> install
> MSI (s) (78:4C) [20:14:06:466]: Determined that existing product (either
> this product or the product being upgraded with a patch) is installed
> per-user.
> MSI (s) (78:4C) [20:14:06:467]: PROPERTY CHANGE: Deleting ALLUSERS property.
> Its current value is '1'.
> MSI (s) (78:4C) [20:14:06:467]: Product
> {F9B07DF3-06A7-4313-BA4D-40B1F046C6C4} is not managed.
> ...
> MSI (s) (78:4C) [20:14:06:467]: PROPERTY CHANGE: Adding ProductState
> property. Its value is '1'.
> MSI (s) (78:4C) [20:14:06:467]: Entering
> CMsiConfigurationManager::SetLastUsedSource.
> MSI (s) (78:4C) [20:14:06:467]: Specifed source is already in a list.
> MSI (s) (78:4C) [20:14:06:467]: User policy value 'SearchOrder' is 'nmu'
> MSI (s) (78:4C) [20:14:06:467]: Adding new sources is allowed.
> MSI (s) (78:4C) [20:14:06:467]: Package name retrieved from configuration
> data: 'wpkg-gp-0.5_x64.msi'
>
> After the sequence table is parsed (relevant lines):
>
> Action start 20:14:06: INSTALL.
> MSI (s) (78:4C) [20:14:06:552]: Running ExecuteSequence
> MSI (s) (78:4C) [20:14:06:554]: Doing action: FindRelatedProducts
> MSI (s) (78:4C) [20:14:06:555]: FindRelatedProducts: current install is
> per-user. Related install for product
> '{A70E99ED-87C6-4142-88A7-8491459494A2}' is per-machine. Skipping...
>
> That suggests to me three things:
>
> 1. 0.3.0 is installed per-machine.
> 2. 0.5.0 MSI is intended to be installed per-machine based on the initial
> value of ALLUSERS in the property table.
> 3. 0.5.0 MSI is installing per-user. The reason appears to be that the 0.5.0
> MSI has been advertised into the per-user context before being installed.
> ProductState property value means INSTALLSTATE_ADVERTISED 1 "The product is
> advertised but not installed."
>
> Whatever tool you are using to place the MSIs is advertising them into a
> different context than you want. You need to fix that. It isn't your MSI, it
> is your usage of the tool that you use to prepare for the installation. That
> tool (wpkg?) is overriding your per-machine preference.
>
> Blair
>
Hi Blair,
Thank you very much, that kind of proves my suspicion, which i didn't
want to believe. I don't think the problem is not with wpkg as such but
with wpkg-gp, which is a GPE client that installs/updates various
packages, and with the context its running in. In this case its trying
to update itself. The new files actually appear in the correct place and
AFAICS things work correctly, but overall this can't be deemed as
successful update.
What really confused me initially, was that some of the msi's and most
of the apps that i have used did update correctly (for example
TortoiseSVN msi's).
Kind Regards
Luk
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
