Kbase P75349: Progress Explorer missing 'Databases' node
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
06/04/2004 |
|
Status: Unverified
SYMPTOM(s):
Progress Explorer missing 'Databases' node
License Summary option on the server node in the Progress Explorer shows the
correct database license
admserv.log file contains error that database plugin is not installed
Exception in the ads0.exp shows that the adminport socket was in use causing
the bind to fail
Errors found in the admserv.log file:
[*UnexpectedError*] * recorded as exception #1 in file ads0.exp.
[AdminServer] * DatabasePlugin not installed: Plugin asked not to be installed. (ADMMsg014)
Exception recorded in the ads0.exp :
Exception at Tue Apr 06 11:11:43 GMT+02:00 2004: java.net.BindException
Message (throw): Failed to establish remote socket connection.
Message (excp): Address in use: JVM_Bind
Stack Trace:
java.net.BindException: Address in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:397)
at java.net.ServerSocket.<init>(ServerSocket.java:170)
at java.net.ServerSocket.<init>(ServerSocket.java:82)
at com.progress.common.comsock.ServerComSock.connect(ServerComSock.java:42)
at com.progress.juniper.admin.JAPlugIn.initSocket(JAPlugIn.java:322)
at com.progress.juniper.admin.JAPlugIn.init(JAPlugIn.java:502)
at com.progress.chimera.adminserver.AdminServer.installPlugin(AdminServer.java:1113)
at com.progress.chimera.adminserver.AdminServer.installPlugins(AdminServer.java:946)
at com.progress.chimera.adminserver.AdminServer.setupPlugins(AdminServer.java:521)
at com.progress.chimera.adminserver.AdminServer.<init>(AdminServer.java:328)
at com.progress.chimera.adminserver.AdminServer.<init>(AdminServer.java:147)
at com.progress.chimera.adminserver.NTAdminServer.<init>(NTAdminServer.java:74)
at com.progress.chimera.adminserver.NTAdminServer.main(NTAdminServer.java:348)
CAUSE:
Another process occupied the default AdminServer's adminport right after the
AdminServer has started.
FIX:
Stop the process using the default AdminServer's adminport before starting
the AdminServer, or use another value for that port number i.e.
proadsv -start -adminport 23456
where the '23456' can be any port number that is not in use on the system.