Kbase P166053: Trying to enable an AdminServer as a remote container in OpenEdge Explorer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/05/2011 |
|
Status: Verified
SYMPTOM(s):
Unable to enable AdminServer as a remote container in OpenEdge Management/OpenEdge Explorer
Trying to view a remote AdminServer using OpenEdge Explorer
The remote container is not listed in OpenEdge Explorer/Openedge Management console
The remote container does not show up in OpenEdge Explorer
Fmconfig ?enable fails with error SonicMQ install failed on the remote server
SonicMQ install failed
fmconfig -host -enable completes sucessfully but contains the following messages:
Argument -host is valid only for the remote Adminserver.
Argument ignored: -host <remote hostname>
fmconfig -query shows that status enabled in the OpenEdge Management/OpenEdge Explorer machine
Unable to see remote container after enabling it with fmconfig sucessfully
FACT(s) (Environment):
OpenEdge Management or OpenEdge Explorer Tool is installed.
UNIX
OpenEdge 10.2B
OpenEdge Explorer 10.2x
CAUSE:
If either OpenEdge Explorer or OpenEdge Management are installed, they must be disassociated AdminServer in order
for it to be accessed by a remote OpenEdge Explorer/OpenEdge Management.
Starting in OpenEdg 10.2B the OpenEdge Explorer can installed and automaticaly glued to the OpenEdge install
FIX:
On the remote server:
1. cd to $DLC/bin
2. run proenv
At the proenv prompt run the following commands:
3.fmconfig -disable
4.unglue
5.fmconfig -enable -host [hostname] -debug
6. Restart the AdminServer
proadsv -start
On the local system:
The remote AdminServer should now show up in OpenEdge Explorer.