Updater.exe fails with newer version installed - incorrect

[bkavanaugh]

We have switched our version numbering scheme from something like 5.38.11.2 to a date-based one, e.g., 2015.804.2200.2. The initial update from the old version numbering scheme to the new one was fine, but in our test environment users are reporting they are getting the error that a newer version is already installed, and it exits out. The user in the attached log was attempting to upgrade from 2015.722.2200.2 to 2015.804.2200.2, for example. I don't see why it thinks the former is more recent than the latter. Is 2015 too large for the major version number, or is something else wrong here?

[Dan]

Hello,

Please note that the format of the ProductVersion is as follow:

• major.minor.build

The first field is the major version and has a maximum value of 255. The second field is the minor version and has a maximum value of 255. The third field is called the build version or the update version and has a maximum value of 65,535.

So, the given version numbering scheme date-based 2015.804.2200.2 is not a valid format for the ProductVersion.

If you have other questions, please let us know.

Best regards,
Dan