Re: [WiX-users] Patching and null KeyPath
Generally, I put my service authoring in the same component as the File element
referencing the service binary. That way, the KeyPath is the service binary,
and I don't have these issues.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: vcur...@hotmail.com [mailto:vcur...@hotmail.com]
Sent: Thursday, January 22, 2015 1:42 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching and null KeyPath
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
NOTICE: This electronic mail message and any files transmitted with it are
intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged
information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
--
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
Need more information. What is the authoring for the component installing the file? What is the actual path to the file in both A and B cases? In the authoring, is the file the KeyPath, or is another file or registry entry the KeyPath? -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: vcur...@hotmail.com [mailto:vcur...@hotmail.com] Sent: Wednesday, January 21, 2015 2:19 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Patching and null KeyPath 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 NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- 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
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
