Kbase P123424: fmconfig -enable -host fails when trying to add a new remote container to be monitored by OE Managem
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/11/2007 |
|
Status: Verified
FACT(s) (Environment):
OpenEdge Management 3.1B
OpenEdge 10.1B
OpenEdge 10.1A
OpenEdge 10.0B
Progress 9.1E
SYMPTOM(s):
fmconfig -enable -host fails when trying to add a new remote container to be monitored by OE Management
Creating new container for host: remotehost ... Failure
ERROR: Failed to create new container configuration, adminserver is NOT enabled for remote monitoring.
MFConfigurationElements.xsd is present in DLC folder
No files have been created in WRKDIR working directory
fmconfig has been executed within proenv
Service packs 1 was installed on the OE Management AdminServer
No errors are recorded in admserv.log and/or other log files
OE Management is running and has been enabled for remote monitoring
CAUSE:
Missing installation of an appropriate SP or TFix on a remote machine - since OE Management machine has been upgraded to SP1 (3.1B01 and 10.1B01), the remote monitoring is now using SonicMQ 6.1, the remote machine is still running SonicMQ 5.0.1 - hence the connection problem.
FIX:
In order to fix the problem:
1) run proenv -> "fmconfig -disable"
2) delete DLC/properties/management.properties and DLC/MFConfigurationElements.xsd
3) install the appropriate SP or TFix on the installation you want to remotely monitor by OE Management - check a solution on What TFixes contain OpenEdge Management remote monitoring upgrade ? for more info
4) re-run proenv -> "fmconfig -enable -host <oemhost>"
5) start the AdminServer