Kbase P130816: Unable to start OpenEdge Management AdminServer after running fmconfig -enable
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
01/07/2008 |
|
Status: Unverified
SYMPTOM(s):
Unable to start OpenEdge Management AdminServer after running fmconfig -enable
OpenEdge Management AdminServer will start after running fmconfig -disable
Removed vpd.properties file
Removed existing MFConfigurationElements.xsd file
No Java process spawned
Only one message in the admserv.log file
Instantiating management framework container...
FACT(s) (Environment):
OpenEdge 10.1B
OpenEdge Management 3.1B 32-bit
OpenEdge Management 3.1B 64-bit
CAUSE:
User is running 10.1B01 or higher with OpenEdge Management 3.1B. In 3.1B01, OpenEdge management began using Sonic 6.0 as the broker for remote monitoring. This requires the base OpenEdge install to be at a similar level to provide the proper supporting files. In this instance, the Sonic 5 broker is mixing with Sonic 6 files.
FIX:
Upgrade the OpenEdge Management installation to 3.1B01 or higher.