Re: [WiX-users] Major upgrade: a few files are not installed
No problem. This is what we do for our customers every day at FireGiant
(although FireGiant answers are far more detailed than the 1-2 sentences I have
time to write here).
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Lukas Rieger [mailto:lrie...@nemetschek-engineering.at]
Sent: Friday, April 24, 2015 11:33 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Major upgrade: a few files are not installed
I thought it treated files like MSIs and only compared the first three digits,
so I glanced over the version number. Comparing them again, OLD > NEW.
File Table |File| Component_
| FileName| FileSize | Version
---|
---|
---|
old MSI|fileEcMWtDjRdBXxvVHY.WvW_XXJI4GZcq5iAszC_F3KIwk |
Cj9pc73bMjDSVVGUqS81_nPSltSFuUEweshtzct2AHi4 | bftlang.dll | 118784 |
2004.553.4453.1067
new MSI|fileYXlC3cFPRwh6qrJ5u..Ll052XUiMylAmA6a4BwMlz_o |
CZJsalkL4nX.r6JS5xXH3pjmr9mY1AO4CITmUEHjP82I | bftlang.dll | 118784 |
2004.553.4453.1064
Component Table |Component|
ComponentId| KeyPath
|---
|---
|-
old MSI |Cj9pc73bMjDSVVGUqS81_nPSltSFuUEweshtzct2AHi4 |
{C45097D5-E359-48B5-9F85-AB5EC81D62BF} |
filepcu3NI3UMnsXucCthGSqTSHMvUoyVuyQHRbEXnUVii0
new MSI |CZJsalkL4nX.r6JS5xXH3pjmr9mY1AO4CITmUEHjP82I |
{8B97BC16-7D4D-45CD-A3E3-903C60868202} |
fileYXlC3cFPRwh6qrJ5u..Ll052XUiMylAmA6a4BwMlz_o
MSI (s) (88:A0) [20:12:50:115]: Disallowing installation of component:
{8B97BC16-7D4D-45CD-A3E3-903C60868202} since the same component with higher
versioned keyfile exists
Now that log entry finally makes sense...
*head->table*
Thank you!
So I guess the question becomes how to best downgrade a file during a major
upgrade...
We have no shared components or merge modules, so we always want to put exactly
the version in the msi on disk, even if that means downgrading.
At least according to this (
http://stackoverflow.com/questions/4227456/windows-installer-deletes-versioned-file-during-product-upgrade-instead-of-down?rq=1
) post, scheduling before Costing should work, so I will try that.
Thank you again,
Lukas
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major upgrade: a few files are not installed
I thought it treated files like MSIs and only compared the first three
digits, so I glanced over the version number. Comparing them again, OLD >
NEW.
File Table |File| Component_
| FileName| FileSize | Version
---|
old MSI|fileEcMWtDjRdBXxvVHY.WvW_XXJI4GZcq5iAszC_F3KIwk |
Cj9pc73bMjDSVVGUqS81_nPSltSFuUEweshtzct2AHi4 | bftlang.dll | 118784 |
2004.553.4453.1067
new MSI|fileYXlC3cFPRwh6qrJ5u..Ll052XUiMylAmA6a4BwMlz_o |
CZJsalkL4nX.r6JS5xXH3pjmr9mY1AO4CITmUEHjP82I | bftlang.dll | 118784 |
2004.553.4453.1064
Component Table |Component|
ComponentId| KeyPath
|---
old MSI |Cj9pc73bMjDSVVGUqS81_nPSltSFuUEweshtzct2AHi4 |
{C45097D5-E359-48B5-9F85-AB5EC81D62BF} |
filepcu3NI3UMnsXucCthGSqTSHMvUoyVuyQHRbEXnUVii0
new MSI |CZJsalkL4nX.r6JS5xXH3pjmr9mY1AO4CITmUEHjP82I |
{8B97BC16-7D4D-45CD-A3E3-903C60868202} |
fileYXlC3cFPRwh6qrJ5u..Ll052XUiMylAmA6a4BwMlz_o
MSI (s) (88:A0) [20:12:50:115]: Disallowing installation of component:
{8B97BC16-7D4D-45CD-A3E3-903C60868202} since the same component with
higher versioned keyfile exists
Now that log entry finally makes sense...
*head->table*
Thank you!
So I guess the question becomes how to best downgrade a file during a
major upgrade...
We have no shared components or merge modules, so we always want to put
exactly the version in the msi on disk, even if that means downgrading.
At least according to this (
http://stackoverflow.com/questions/4227456/windows-installer-deletes-versioned-file-during-product-upgrade-instead-of-down?rq=1
) post, scheduling before Costing should work, so I will try that.
Thank you again,
Lukas
Von:Rob Mensching
An: "General discussion about the WiX toolset."
Datum: 24.04.2015 20:13
Betreff: Re: [WiX-users] Major upgrade: a few files are not
installed
Windows Installer only ignores the 4th digit of the MSI version. It'll
evaluate all four places of a file version.
_
Short replies here. Complete answers over there:
http://www.firegiant.com/
-Original Message-
From: Lukas Rieger [mailto:lrie...@nemetschek-engineering.at]
Sent: Friday, April 24, 2015 10:59 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Major upgrade: a few files are not installed
I opened up both MSIs in Orca and compared their version numbers.
The missing files are different, but their version only differs in the
forth place (which is ignored by MSI). The fourth place of the upgrading
files is actually higher, so there are no higher version components on
disk.
Files which are exactly the same (same hash and of course same version
number) do exist on disk after the upgrade.
Files whose version differs in the first three places are also correctly
replaced.
The affected DLLs are kind of like third party - they are built
internally, but the version number is defined by the incremental build and
I have no way to change the versioning algorithm (different team, ...).
I have also googled some more, and one option seems to be to schedule
RemoveExistingProducts even earlier, before costing. Would there be any
downside to that?
Sorry to take so long to follow up and thank you, Lukas
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major upgrade: a few files are not installed
Windows Installer only ignores the 4th digit of the MSI version. It'll evaluate all four places of a file version. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Lukas Rieger [mailto:lrie...@nemetschek-engineering.at] Sent: Friday, April 24, 2015 10:59 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Major upgrade: a few files are not installed I opened up both MSIs in Orca and compared their version numbers. The missing files are different, but their version only differs in the forth place (which is ignored by MSI). The fourth place of the upgrading files is actually higher, so there are no higher version components on disk. Files which are exactly the same (same hash and of course same version number) do exist on disk after the upgrade. Files whose version differs in the first three places are also correctly replaced. The affected DLLs are kind of like third party - they are built internally, but the version number is defined by the incremental build and I have no way to change the versioning algorithm (different team, ...). I have also googled some more, and one option seems to be to schedule RemoveExistingProducts even earlier, before costing. Would there be any downside to that? Sorry to take so long to follow up and thank you, Lukas -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major upgrade: a few files are not installed
I opened up both MSIs in Orca and compared their version numbers. The missing files are different, but their version only differs in the forth place (which is ignored by MSI). The fourth place of the upgrading files is actually higher, so there are no higher version components on disk. Files which are exactly the same (same hash and of course same version number) do exist on disk after the upgrade. Files whose version differs in the first three places are also correctly replaced. The affected DLLs are kind of like third party - they are built internally, but the version number is defined by the incremental build and I have no way to change the versioning algorithm (different team, ...). I have also googled some more, and one option seems to be to schedule RemoveExistingProducts even earlier, before costing. Would there be any downside to that? Sorry to take so long to follow up and thank you, Lukas Von:Rob Mensching An: "General discussion about the WiX toolset." Datum: 14.04.2015 02:49 Betreff: Re: [WiX-users] Major upgrade: a few files are not installed You should root cause why higher version Components exist on the machine since you scheduled upgrade early. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Lukas Rieger [mailto:lrie...@nemetschek-engineering.at] Sent: Monday, April 13, 2015 2:29 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Major upgrade: a few files are not installed Sorry, I forgot to mention that I am using Burn as Bootstrapper, so I can't control the REINSTALLMODE Thank you, Lukas -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major upgrade: a few files are not installed
In the original post, it says that all the guids are being generated programmatically (and the component rules are not followed, but that isn't too significant if REP is early). So why is it disallowing installation of a component id (because a a higher version is installed) if all the guids in the upgrade are supposedly different (System.Guid.NewGuid) from the installed product? Both can't be true. Either all the guids in the upgrade are different from all the ones in the installed product and there is no overlap, or there are some components with identical guids in both original and upgrade, causing this issue, to which the solution appears to be to give them a new Guid so that all the guids in the upgrade are diifferent from the installed product. --- Phil Wilson On Mon, Apr 13, 2015 at 5:54 PM, Rob Mensching wrote: > You should root cause why higher version Components exist on the machine > since you scheduled upgrade early. > > _ > Short replies here. Complete answers over there: http://www.firegiant.com/ > > -Original Message- > From: Lukas Rieger [mailto:lrie...@nemetschek-engineering.at] > Sent: Monday, April 13, 2015 2:29 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Major upgrade: a few files are not installed > > Sorry, I forgot to mention that I am using Burn as Bootstrapper, so I can't > control the REINSTALLMODE > > Thank you, > Lukas > > -- > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major upgrade: a few files are not installed
You should root cause why higher version Components exist on the machine since you scheduled upgrade early. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Lukas Rieger [mailto:lrie...@nemetschek-engineering.at] Sent: Monday, April 13, 2015 2:29 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Major upgrade: a few files are not installed Sorry, I forgot to mention that I am using Burn as Bootstrapper, so I can't control the REINSTALLMODE Thank you, Lukas -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major upgrade: a few files are not installed
Sorry, I forgot to mention that I am using Burn as Bootstrapper, so I
can't control the REINSTALLMODE
Thank you,
Lukas
Von:Joel Budreau
An: lrie...@nemetschek-engineering.at
Kopie: "General discussion about the WiX toolset."
Datum: 13.04.2015 23:21
Betreff: Re: [WiX-users] Major upgrade: a few files are not
installed
You could pass REINSTALLMODE=amus so that all files are overwritten by the
newer MSI -
https://msdn.microsoft.com/en-us/library/aa371182%28v=vs.85%29.aspx
> On Apr 13, 2015, at 9:36 AM, Lukas Rieger
wrote:
>
> I have the same issue as described here:
>
http://stackoverflow.com/questions/15138731/wix-major-upgrade-not-installing-all-files
> After a major upgrade a few files are missing. After a repair, they
> reapper, and with a clean install, they are also correctly installed.
> The log contains
> Disallowing installation of component: {GUID-OF-COMPONENT} since the
same
> component with higher versioned keyfile exists
>
> The remove is currently scheduled as afterInstallInitialize.
>
> To make sure that all files are really updated, I use this pattern for
> each file:
>
> Source="#source#" />
>
>
> Basically I want to just write all files contained in the MSI to disk,
> overwriting all existing files.
> Guids and IDs are generated by System.Guid.NewGuid(), so the component
> rules are totally violated and I can't just change the scheduling of
> removeExisting.
>
> What are my options to solve the issue?
> I know I could use a stable ID/Guid generation algorithm (I could
probably
> just use the one provided by Wix) so that the component rules are no
> longer violated and schedule it afterInstallExecute (or Finalize), but I
> would like to keep the current sequence where it is first uninstalled
and
> then cleanly reinstalled.
>
> Thank you,
> Lukas
>
--
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major upgrade: a few files are not installed
You could pass REINSTALLMODE=amus so that all files are overwritten by the
newer MSI - https://msdn.microsoft.com/en-us/library/aa371182%28v=vs.85%29.aspx
> On Apr 13, 2015, at 9:36 AM, Lukas Rieger
> wrote:
>
> I have the same issue as described here:
> http://stackoverflow.com/questions/15138731/wix-major-upgrade-not-installing-all-files
> After a major upgrade a few files are missing. After a repair, they
> reapper, and with a clean install, they are also correctly installed.
> The log contains
> Disallowing installation of component: {GUID-OF-COMPONENT} since the same
> component with higher versioned keyfile exists
>
> The remove is currently scheduled as afterInstallInitialize.
>
> To make sure that all files are really updated, I use this pattern for
> each file:
>
> Source="#source#" />
>
>
> Basically I want to just write all files contained in the MSI to disk,
> overwriting all existing files.
> Guids and IDs are generated by System.Guid.NewGuid(), so the component
> rules are totally violated and I can't just change the scheduling of
> removeExisting.
>
> What are my options to solve the issue?
> I know I could use a stable ID/Guid generation algorithm (I could probably
> just use the one provided by Wix) so that the component rules are no
> longer violated and schedule it afterInstallExecute (or Finalize), but I
> would like to keep the current sequence where it is first uninstalled and
> then cleanly reinstalled.
>
> Thank you,
> Lukas
> --
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Major upgrade: a few files are not installed
I have the same issue as described here:
http://stackoverflow.com/questions/15138731/wix-major-upgrade-not-installing-all-files
After a major upgrade a few files are missing. After a repair, they
reapper, and with a clean install, they are also correctly installed.
The log contains
Disallowing installation of component: {GUID-OF-COMPONENT} since the same
component with higher versioned keyfile exists
The remove is currently scheduled as afterInstallInitialize.
To make sure that all files are really updated, I use this pattern for
each file:
Basically I want to just write all files contained in the MSI to disk,
overwriting all existing files.
Guids and IDs are generated by System.Guid.NewGuid(), so the component
rules are totally violated and I can't just change the scheduling of
removeExisting.
What are my options to solve the issue?
I know I could use a stable ID/Guid generation algorithm (I could probably
just use the one provided by Wix) so that the component rules are no
longer violated and schedule it afterInstallExecute (or Finalize), but I
would like to keep the current sequence where it is first uninstalled and
then cleanly reinstalled.
Thank you,
Lukas
--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
