[wix-users] error LGHT0204: ICE61: Upgrade.VersionMax cannot be less than Upgrade.VersionMin

Fri Dec 18 13:02:41 PST 2015

Although the error messages says that a product major greater than 127 is supported, that has never been my experience.  I have treated version numbers for C++ and MSI as signed byte, byte, word, signed word.  That works out to 0-127, 0-255, 0-65535, 0-32767.

But, going with the error message I recently saw when one of my developers tried to assign 2015.1.x.0 to an installer, it is a bug.  Not seen it myself, but this should be a supported version number not withstanding my earlier comments.

--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise Notification Service
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |JoCooper at jackhenry.com<mailto:JoCooper at jackhenry.com>

From: K. Peters [mailto:kai.peters at gmail.com]
Sent: Friday, December 18, 2015 1:59 PM
To: John Cooper <JoCooper at jackhenry.com>
Subject: Re: Re[2]: [wix-users] error LGHT0204: ICE61: Upgrade.VersionMax cannot be less than Upgrade.VersionMin

The e-mail below is from an external source.  Please do not open attachments or click links from an unknown or suspicious origin.
We have been using it - more or less as described - successfully for years. Not claiming correctness, though - but it has worked well for us.

I just ran a couple of tests and I can now say with certainty that it stops working as soon as major is > 127

I can do:

    <?define ProductVersion="127.99.0" ?>

    <UpgradeVersion
        Minimum="1.0.0"
        Maximum="$(var.ProductVersion)"
        IncludeMinimum="yes"
        IncludeMaximum="no"

just fine.

The moment I go up to:

    <?define ProductVersion="128.1.0" ?>

or higher, it breaks.  Should this be considered a bug, or is it a feature?

On Fri, Dec 18, 2015 at 11:11 AM, John Cooper <JoCooper at jackhenry.com<mailto:JoCooper at jackhenry.com>> wrote:
Ok, that is helpful.  It is unusual (although not unheard of) to use both MajorUpgrade and UpgradeVersion.  It might be helpful to know what you are trying to accomplish with the UpgradeVersion element.  It just feels to me like it isn’t sufficiently exclusive.

--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise Notification Service
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |JoCooper at jackhenry.com<mailto:JoCooper at jackhenry.com>

From: K. Peters [mailto:kai.peters at gmail.com<mailto:kai.peters at gmail.com>]
Sent: Friday, December 18, 2015 12:21 PM
To: John Cooper <JoCooper at jackhenry.com<mailto:JoCooper at jackhenry.com>>
Subject: Re: Re[2]: [wix-users] error LGHT0204: ICE61: Upgrade.VersionMax cannot be less than Upgrade.VersionMin

The e-mail below is from an external source.  Please do not open attachments or click links from an unknown or suspicious origin.
Thanks John,

should I have shared a bit more code (we are using MajorUpgrade like this):

    <MajorUpgrade
        Schedule="afterInstallValidate"
        AllowDowngrades="no"
        DowngradeErrorMessage="A newer version of [ProductName] is already installed." />

    <Upgrade Id="$(var.WrongUpgradeCode)">
      <!-- UpgradeVersion Minimum="$(var.Version)" OnlyDetect="yes" Property="NEWERVERSIONDETECTED" / -->
      <UpgradeVersion
        Minimum="1.0.0"
        Maximum="$(var.MaximumUpgradeVersion)"
        IncludeMinimum="yes"
        IncludeMaximum="yes"
        Property="WRONGUPGRADECODEPRODUCT" />
    </Upgrade>

If I set MaximumUpgradeVersion to 3.1.6 (which is the version before the current, which is 214.2.0), it works fine.
The moment I set MaximumUpgradeVersion to 214.2.0, i.e. current it breaks....

  <?define MaximumUpgradeVersion="3.1.6" ?>
  <?define ProductCode="*" ?>
  <?define ProductVersion="214.3.0" ?>

On Fri, Dec 18, 2015 at 7:20 AM, John Cooper <JoCooper at jackhenry.com<mailto:JoCooper at jackhenry.com>> wrote:
It is much easier to use the MajorUpgrade element.

When using Upgrade and UpgradeVersion, this is generally the pattern:

<!– Major upgrade –>
<Upgrade Id="$(var.UpgradeCode)">
    <UpgradeVersion Minimum="$(var.ProductVersion)" OnlyDetect="yes" Property="NEWERVERSIONDETECTED" />
    <UpgradeVersion Minimum="1.0.0" IncludeMinimum="yes" Maximum="$(var.ProductVersion)" IncludeMaximum="no" Property="OLDERVERSIONBEINGUPGRADED" />
</Upgrade>

<InstallExecuteSequence>
    <RemoveExistingProducts After="InstallInitialize" />
</InstallExecuteSequence>

<Condition Message="!(loc.NewerVersionDetected)">
    NOT NEWERVERSIONDETECTED
</Condition>

You will notice that two UpgradeVersion elements are generally used.  Also notice that the current version of the MSI is used for both elements.   The future version is what is probably giving you problems.

--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise Notification Service
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |JoCooper at jackhenry.com<mailto:JoCooper at jackhenry.com>

-----Original Message-----
From: kpeters [mailto:kai.peters at gmail.com<mailto:kai.peters at gmail.com>]
Sent: Friday, December 18, 2015 9:10 AM
To: John Cooper <JoCooper at jackhenry.com<mailto:JoCooper at jackhenry.com>>
Subject: Re[2]: [wix-users] error LGHT0204: ICE61: Upgrade.VersionMax cannot be less than Upgrade.VersionMin

The e-mail below is from an external source.  Please do not open attachments or click links from an unknown or suspicious origin.

We are on 214.2.0 abd I am building for the next (214.3.0) release

------ Original Message ------
From: "John Cooper" <JoCooper at jackhenry.com<mailto:JoCooper at jackhenry.com>>
To: "kpeters" <kai.peters at gmail.com<mailto:kai.peters at gmail.com>>; "WiX Toolset Users Mailing List"
<wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Sent: 2015-12-18 05:51:14
Subject: RE: [wix-users] error LGHT0204: ICE61: Upgrade.VersionMax cannot be less than Upgrade.VersionMin

>What is the current product version?
>
>--
>John Merryweather Cooper
>Senior Software Engineer | Integration Development Group | Enterprise
>Notification Service Jack Henry & Associates, Inc.® | Lenexa, KS  66214
>| Ext: 431050
>|JoCooper at jackhenry.com<mailto:JoCooper at jackhenry.com> <mailto:%7CJoCooper at jackhenry.com<mailto:7CJoCooper at jackhenry.com>>
>
>
>
>-----Original Message-----
>From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org<mailto:wix-users-bounces at lists.wixtoolset.org>] On
>Behalf Of kpeters
>Sent: Thursday, December 17, 2015 10:02 PM
>To: wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>
>Subject: [wix-users] error LGHT0204: ICE61: Upgrade.VersionMax cannot
>be less than Upgrade.VersionMin
>
>The e-mail below is from an external source.  Please do not open
>attachments or click links from an unknown or suspicious origin.
>
>      I have:
>      ...
>      <?define MaximumUpgradeVersion="214.2.0" ?>
>      <?define ProductCode="*" ?>
>      <?define ProductVersion="214.3.0" ?>
>      ...
>      <Upgrade Id="$(var.WrongUpgradeCode)">
>        <UpgradeVersion
>          Minimum="1.0.0"
>          Maximum="$(var.MaximumUpgradeVersion)"
>          IncludeMinimum="yes"
>          IncludeMaximum="yes"
>          Property="WRONGUPGRADECODEPRODUCT" />
>      </Upgrade>
>      ...
>
>      I receive:
>
>      error LGHT0204: ICE61: Upgrade.VersionMax cannot be less than
>Upgrade.VersionMin (WRONGUPGRADECODEPRODUCT)
>
>      How is "214.3.0" less than "214.2.0" ?
>
>      Am probably way off somewhere....
>
>____________________________________________________________________
>WiX Toolset Users Mailing List provided by FireGiant
>http://www.firegiant.com/
>
>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.
>

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.

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.