32-bit Adminservice fails to start after installing 11.5 64-bit

32-bit Adminservice cannot start after installing 11.5 64-bit
Unable to restart 32-bit AdminService.
When OpenEdge 11.5 64-bit is uninstalled, 32-bit AdminService starts.
After uninstalling OpenEdge 11.5 jar files are left in the 115\java\ext and 115/java directories.
Files in the 115\java\ext and 115\java directory can only be removed after stopping the 32-bit AdminService.
admserv.log file ends with: "AdminServer failed to start"
32-bit AdminServer fails to start with No exceptions or error messages apart from "AdminServer failed to start"

No AdminServer Port conflicts between installed versions.
Install directories for OpenEdge versions are distinct.

1. When 11.5 64-bit is installed, 11.5 keys are appended to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC (where 32-bit keys are housed). The relevant 32-bit keys are not overwritten.
2. During the tailoring phase, the 32-bit version AdminServerPlugins.properties are updated with 11.5 OEE references

OpenEdge 11.6.0 64-bit corrected the appropriate Registry Keys to be updated, so that the tailoring phase correctly populates the related properties files.

Before installing OpenEdge 64-bit on the same machine as any OpenEdge 32-bit version:

• Backup the OpenEdge 32-bit keys: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC
• Backup the OpenEdge 32-bit DLC\properties

0.   Backup the registry as a precaution.

1.   If OpenEdge 11.5 32-bit is not also installed with the OpenEdge 11.5 64-bit version, then remove the following keys:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC\OpenEdge\11.05.000]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC\PROGRESS\11.5]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC\PROGRESS\11.5\JAVA]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC\PROGRESS\11.5\Startup]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC\ProShell\11.5]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC\ProShell\11.5\Font] 

2. The AdminServerPlugins.properties needs to be reverted to the 32-bit version. Ideally these need to be sourced from another install.

The affected sections are:

[PluginPolicy.ActiveMQC]
Which should not be present prior OpenEdge 11.3 where it is required for remote management

[PluginPolicy.Fathom]
classpath= (points to the 115 jar files in the 115 OEE/OEM install directory, and 115 DLC/java and java/ext directories)

 

Progress Article: 

OpenEdge 11.5 SP1 64-Bit overwrites 32-Bit registry   
OpenEdge 64 bit showcfg.exe shows 32-bit licenses instead of 64-bit OpenEdge 11.x licenses