Exit Code 1603: A newer version of this application is already installed on this computer

Attempting to upgrade many old BES Clients from V To V9.1.1233.0, I’m getting errors in the Log Upgrade:

InstallShield 20:52:04: M **Endpoint Manager Client {E3EAF0DE-4E03-43C5-82C7-DDC9B84CCF1C} 0 9.1.1233.0 Related
InstallShield 20:52:04: ALLUSERS of related product {E3EAF0DE-4E03-43C5-82C7-DDC9B84CCF1C} is = 1
InstallShield 20:52:04: End SetAllUsers()
MSI (s) (F0:28) [20:52:04:477]: Doing action: AppSearch
Action ended 20:52:04: ISSetAllUsers. Return value 1.
Action start 20:52:04: AppSearch.
MSI (s) (F0:28) [20:52:04:480]: Note: 1: 1322 2:
MSI (s) (F0:28) [20:52:04:480]: Note: 1: 1322 2:
MSI (s) (F0:28) [20:52:04:481]: PROPERTY CHANGE: Adding BESCLIENT_EXISTS property. Its value is ‘C:\Program Files\BigFix Enterprise\BES Client\BESClient.exe’.
MSI (s) (F0:28) [20:52:04:481]: PROPERTY CHANGE: Adding BIGFIXAGENT_SERVICESTART property. Its value is ‘#2’.
MSI (s) (F0:28) [20:52:04:482]: PROPERTY CHANGE: Adding CLIENTCOMPLIANCE_SITEURL property. Its value is ‘http://patch.marriott.com:52311/cgi-bin/bfgather.exe/actionsite’.
MSI (s) (F0:28) [20:52:04:482]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BES Installation Generator 3: 2
MSI (s) (F0:28) [20:52:04:482]: PROPERTY CHANGE: Adding PREVIOUS_BESCLIENT_INSTALLPATH property. Its value is ‘C:\Program Files\BigFix Enterprise\BES Client'.
MSI (s) (F0:28) [20:52:04:482]: PROPERTY CHANGE: Adding PREVIOUS_BIGFIXAGENT_VERSION property. Its value is '’.
MSI (s) (F0:28) [20:52:04:482]: Doing action: LaunchConditions
Action ended 20:52:04: AppSearch. Return value 1.
Action start 20:52:04: LaunchConditions.
MSI (s) (F0:28) [20:52:04:483]: Skipping action: imm_err_AbortInstallIfAgentExists (condition is false)
MSI (s) (F0:28) [20:52:04:483]: Skipping action: imm_err_OSNotSupported (condition is false)
MSI (s) (F0:28) [20:52:04:483]: Doing action: FindRelatedProducts
Action ended 20:52:04: LaunchConditions. Return value 1.
Action start 20:52:04: FindRelatedProducts.
MSI (s) (F0:28) [20:52:04:484]: PROPERTY CHANGE: Adding ISFOUNDNEWERPRODUCTVERSION property. Its value is ‘{E3EAF0DE-4E03-43C5-82C7-DDC9B84CCF1C}’.
MSI (s) (F0:28) [20:52:04:484]: Doing action: ISPreventDowngrade
Action ended 20:52:04: FindRelatedProducts. Return value 1.
Action start 20:52:04: ISPreventDowngrade.
MSI (s) (F0:28) [20:52:04:484]: Product: IBM Endpoint Manager Client – A newer version of this application is already installed on this computer. If you wish to install this version, please uninstall the newer version first. Click OK to exit the wizard.

I’m just not sure why it says 7.1 is newer than 9.1.

Did you use the MSI installer or the EXE installer?

The MSI installers will not upgrade any existing components. You must use the EXE installers to upgrade.

I’m using the BigFix Fixlet:

prefetch BESClientUpgrade.exe sha1:c0926c6f6c77603c9ef453ca8ca025924561fc29 size:10673328 http://software.bigfix.com/download/bes/90/BigFix-BES-Client-9.0.876.0.exe
delete __Local\Get\BESClientUpgrade.exe
// If the next line fails, there is not enough free space to complete this action
continue if {10673328  < free space of drive of client folder of current site}
move __Download\BESClientUpgrade.exe __Local\Get\BESClientUpgrade.exe
// The following line may show as Failed if the command executes a restart of the client - This is normal behaviour on success
wait __Local\Get\BESClientUpgrade.exe /s /v"/l*voicewarmup \"{location of client}\besclientupgrade.log\" REBOOT=ReallySuppress MSIRESTARTMANAGERCONTROL=Disable /qn"

That’s strange. I’ve never seen a newer BES Client refuse to upgrade an older Client installation.

Unless someone else in the Forums has a suggestion, I would recommend opening a PMR with IBM.

1 Like

The pre 9.2 versions (those that incremented their build numbers in the 3rd position) would definitely do this.

The 9.2 and later versions were changed to do a different type of upgrade. Please try a later client.

1 Like

I don’t have an environment that supports 9.2 Clients.
Is there any other option?

If you have an environment that supports 9.1 clients you can run 9.2 clients. You CAN run clients that are newer than the server - many of our customers do - as we only support new OS’s for example on the current releases.

There can be some caveats, new features in the newer clients will not work and there may be some breaks to the rule but a 9.1 server can have 9.2 clients running on it.

1 Like

And… is that supported by IBM?
I remember that configuration exists and it’s possible, but I also remember that IBM doesn’t support that officially.

I’d have to state that I’m not the one who sets support policy but we have other customers here like @jgstew that run production in this way. Unless your servers are WAY off the version (so if you try and run 9.2 with an 8.0 server) I do not believe that it would be unsupported especially if it was 9.1 to 9.2… but again I’m not the person who sets support policy.

@Aram do you know the official policy?

1 Like

@fermt, as @AlanM had indicated, it will work, but for the sake of official support policy:

BigFix Server and BigFix Relays must have an equivalent or higher 
major/minor version than the BigFix Clients (unless explicitly listed 
above or indicated by IBM support)

BigFix Support Policy

1 Like

I’m seeing more issues. After I run the installer of V9.1
It run successfully for some machines, but the old version is not removed and both versions are shown in the Program List, however the current version is directed to the old version.

This is what I can see on the log

MSI (s) (30:68) [12:22:25:900]: Windows Installer reconfigured the product. Product Name: IBM Endpoint Manager Client. Product Version: 9.1.1229.0. Product Language: 1033. Manufacturer: IBM Corp.. Reconfiguration success or error status: 0.

I would probably recommend upgrading to the latest v8.0.x release first, make sure that works, then try upgrading clients to 9.x

v7.x is pretty old at this point, so it doesn’t surprise me that there could be issues upgrading directly from v7.x to v9.x

I definitely run BigFix with clients both older and newer than the Root/Relays. Newer clients especially for newer OSes before the Root/Relay have a chance to get upgraded, which can take a while to schedule.

Hi I have just experienced this same issue. We are at on server and main relays. We have about 57 relays besides and 20 of these refuse to up date from The bulk of servers are on 2008R2 at the moment. The error is self explanatory so has anyone else seen this issue recently.

You’re having the same issue? When this was written, in 2016, I think JGStew’s guidance to upgrade first from 7.x to 8.x and then 9.x was sound. At this point, if you are still on 7.x, I might consider uninstalling it completely and then using the Client Deployment Tool instead to do a new, clean install rather than upgrade from 7.x.