[WiX-users] Patching and null KeyPath

[vcur...@hotmail.com]

Hello. 

I'm having an issue with a patch behaving differently on two machine with
the same target installation.

On one machine (A) the component is action-ed during the patch install and
on the other (B) it is not.

Other components are behaving the same way, I notice that these all have
null KeyPaths in the component table.

(A) is a Server 2008R2 O/S
(B) is a Server 2012 O/S

I have tried multiple combinations of ALLUSER, REINSTALL, and REINSTALLMODE
switches with no luck. 

I am actually looking for the (B) behaviour.

Any ideas on the difference in behaviour?


Action ended 10:26:48: MigrateFeatureStates. Return value 0.
MSI (s) (28:A8) [10:26:48:506]: Feature: Server; Installed: Local;  
Request: Reinstall;   Action: Reinstall
MSI (s) (28:A8) [10:26:48:506]: Component: COMPONENTNAME; Installed: Local;  
Request: Local;   Action: Local


(B)

Action ended 163540 MigrateFeatureStates. Return value 0.
MSI (s) (1C34) [163540699] Feature Server; Installed Local;   Request
Reinstall;   Action Reinstall
MSI (s) (1C34) [163540699] Component COMPONENTNAME; Installed Local;  
Request Null;   Action Null



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-and-null-KeyPath-tp7598944.html
Sent from the wix-users mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patching and null KeyPath

[vcur...@hotmail.com]

The component is a service install\remove. We have not set a KeyPath so I
guess Wix is choosing one, but looking at the component table in InstEd the
KeyPath is null for this component.

The machine (A) that is actioning the component I have found has been
through a few product upgrades whereas the other (B) is a clean install.
Would MigrateFeatureStates be causing the component to be reaction-ed?




Component Id=COMPONENTNAME
   Guid={085BDB56-E445-40A0-BEDA-4D35C1A7C6EF}
   Directory=INSTALLDIR
CreateFolder/
ConditionOLDAPPFOUND/Condition
ServiceControl Id=sclMU_svcName
Name=svcName
Stop=install
Remove=install
Wait=yes /
/Component

Thanks,

V.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-and-null-KeyPath-tp7598944p7598953.html
Sent from the wix-users mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users