Kbase P157082: Can 32-bit and 64-bit Products be installed on the same Windows machine?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/10/2010 |
|
Status: Verified
GOAL:
Can 32-bit and 64-bit OpenEdge Products be installed on the same Windows machine?
GOAL:
Can 32 bit and 64 bit OpenEdge ODBC Drivers be installed on the same Windows machine?
GOAL:
Can 32 bit and 64 bit OpenEdge JDBC Drivers be installed on the same Windows machine?
GOAL:
Can 32-bit and 64-bit OpenEdge Application Server be installed on the same Windows machine?
GOAL:
Can 32-bit and 64-bit OpenEdge Architect be installed on the same Windows machine?
GOAL:
Can 32-bit and 64-bit OpenEdge WebSpeed Messenger be installed on the same Windows machine?
GOAL:
Can 32-bit and 64-bit OpenEdge and OpenEdge Mangement be installed on the same Windows machine?
FACT(s) (Environment):
Windows
x86_64 (AMD64/EMT64)
ia64 (Intel Itanium 64-bit)
x86 (Intel 32-bit)
OpenEdge 10.2x
FIX:
No.
The installer for the 32-bit and 64-bit products will search for an existing installation of the same version on the machine.
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 products to be installed into the same installation directory.
Installation of 32-bit products into the 64-bit installation may corrupt or mix the two bit versions in an incompatible fashion.
Installation of 64-bit products into the 32-bit installation may corrupt or mix the two bit versions in an incompatible fashion.
Using NetSetup also downloads some .dlls in the installation process and would result in an incompatible mixture of 32 and 64 bit dlls.
Possible workarounds are:
#1 Use different OE Version for the server and the client.
If 32-bit and 64-bit products are necessary, consider installing two versions of OpenEdge that are in the same major release.
Example:
Install 32-bit 10.2A into c:\dlc102a
Install 64-bit 10.2B into c:\dlc102b
#2 Use the same OE Version for server and the client, but on different machines
Example:
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 can not connect to each other in shared memory but can communicate using TCP (i.e. startup parameters -H <hostname> -S <service port>.