At present, use of a 32-bit web browser and a 32-bit JRE are required to be able to use the web client from Linux. (See Supported Web Browsers in the Installation Information Readme.)
In VM 8.6.0, the automatic switch breaks when VM is installed on a 32-bit release of Windows. Using a 64-bit release of Windows does not have this problem.
To avoid this error, please: Use the regular 32-bit browser named "Internet Explorer" and not the one that was exclusively built for use with 64-bit plug-ins named "Internet Explorer (64-bit)". Make sure that the Operating System has a 32-bit version of the Java plug-in installed .
This can happen if you are running a 64-bit Linux distribution and did not install the corresponding 32-bit client packages for winbind or sssd. The 32-bit Version Manager application needs access to 32-bit client libraries to prevent a silent failure of the Linux system call getpwuid()
) support packages being installed as well. See Red Hat KB doc 36238 for more information on the need to install 32-bit packages on a 64-bit OS to run 32-bit software. This article also reveals that the list of 32-bit packages that are installed by default changed between RHEL5 and RHEL6.
This error is caused by running a 32-bit ISAPI filter (isapi_redirect.dll) on an IIS server that is configured to only accept 64-bit filters and plug-ins.
Error: could not find libjava.so Error: could not find Java 2 Runtime Environment This is caused by Version Manager attempting to use the old 32-bit JRE that is still located in the installation folder with the new 64-bit libraries, which fails.