Chain Omnissa Access Upgrade Fails During the Preupdate Process

A chain upgrade creates multiple instances of the bc-fips-1.0.x.BC-FIPS-Certified.jar file, which causes an upgrade to fail during the preupdate process.

Problem

When you try to upgrade to Omnissa Access, the following error message appears and the upgrade aborts.

Please validate database permissions and try upgrade again 
The pre-update process failed, upgrade aborted.

Cause

Performing a series of Omnissa Access upgrades might result in the creation of two different jar files, a bc-fips-1.0.0.BC-FIPS-Certified.jar file and a bc-fips-1.0.1.BC-FIPS-Certified.jar. The existence of both files at the same time causes the upgrade to fail.

Solution

1. Go to the /usr/local/horizon/jre-endorsed/ directory.

2. If both the bc-fips-1.0.0.BC-FIPS-Certified.jar file and the bc-fips-1.0.1.BC-FIPS-Certified.jar exist, delete the older version, bc-fips-1.0.0.BC-FIPS-Certified.jar, and perform the upgrade again.