Prior to OpenEdge 11.5, 32-bit OpenEdge and 64-bit OpenEdge versions cannot be installed on the same 64-bit Windows server.
While fundamentally the Operating System may segment 32-bit and 64-bit products to some degree, the installer is not designed to compartmentalize itself appropriately for both 32-bit and 64-bit versions to co-exist.
The installer for the 32-bit and 64-bit products will always first search for an existing installation of the same version on the machine. Since the installer makes no distinction between 32-bit or 64-bit installation, if the same version of Progress / OpenEdge is installed on the system, the installer will only allow additional licenses/products to be installed into the same installation directory of the same bit-version.
- Installation of 32-bit products into the 64-bit installation will corrupt or mix the different bit versions in an incompatible fashion.
- Installation of 64-bit products into the 32-bit installation will corrupt or mix the different bit versions in an incompatible fashion.
NetSetup installations also downloads some .dlls in the installation process and would result in an incompatible mixture of 32 and 64 bit dlls.
OpenEdge 10.2A, 10.2B, 11.0, 11.1, and 11.2, the 64-bit OpenEdge Windows licenses remain "
Server Only" products. Anything that is a client license will remain a 32-bit GUI Client (read: there is no 'prowin64.exe').
Starting with OpenEdge 11.3, a 64-bit GUI client is available. However, both 64-bit and 32-bit versions of the same OpenEdge version cannot be on the same machine until OpenEdge 11.5.
Option 1: Use different OpenEdge Version for the Server and the Client.If 32-bit and 64-bit products are necessary, consider installing two versions of OpenEdge that are from the same Major but different Minor release.
Example:
Install 32-bit 10.2A into c:\dlc102A
Install 64-bit 10.2B into c:\dlc102B
Option 2: Use the same OpenEdge Version for Server and the Client, but on different machinesExample:
Install 32-bit 10.2B into c:\dlc102b on Server1 (which can be either a 32-bit or a 64-bit machine)
Install 64-bit 10.2B into c:\dlc102b on Server2
The two versions cannot connect to each other via shared memory (self-service) but can communicate using TCP where the client uses startup parameters -H <hostname> -S <service port>.
