Kbase 19722: AdminServer Startup Failed. See admserv.log for Details. (8542)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
AdminServer startup failed. See admserv.log for details. (8542)
Failed RMI setup.. (8539)
Java version installed is correct
An ads0.exp file is generated in the AdminServer's working directory.
java.lang.Exception
Message (throw): Failed to register admin server.
Message (excp): Could not start RMI Registry
java.lang.Exception: Could not start RMI Registry
at com.progress.common.rmiregistry.PrimaryRegistryManager.register (PrimaryRegistryManager.java:52)
at com.progress.chimera.adminserver.AdminServer.setupRMI (AdminServer.java:152)
at com.progress.chimera.adminserver.AdminServer.<init> (AdminServer.java:93)
at com.progress.chimera.adminserver.AdminServer.<init> (AdminServer.java:77)
at com.progress.chimera.adminserver.AdminServer.main (AdminServer.java:528)
CAUSE:
Typically, this error occurs if the AdminServer port (by default, 20931) is already in use.
Use OS command 'netstat' to confirm the port is already in use.
The port may be in use if an AdminServer is running, or if you specify proadsv -start -port <portnum> on starting the AdminServer with a port that is already in use.
FIX:
Make the port available again or choose a different port.