Kbase P24246: Adminserver fails to start after installing Progress Service pack to 9.1D installation on a Windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/9/2005 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.1D
Windows 32 Intel
SYMPTOM(s):
AdminServer fails to stay running after applying service pack
proadsv -start starts AdminServer but query of the AdminServer indicates it is not alive
Either (7900) error occurs in admserv log file or the last entry references the osmetrics.dll
java.net.ConnectException: Connection refused: no further information (7900)
Admserv.log file contains the below Java stacktrace
java.lang.UnsatisfiedLinkError: jniGetOSMetricsVersion at com.progress.osmetrics.OSMetricsImpl.jniGetOSMetricsVersion(Native Method)
Error (8336) occurs when connecting via Progress Explorer
Unable to connect to Admin Server. Ensure Admin Server is running. (8336)
Ads0.exp file contains:
Message (throw): An Exception occurred while loading the osmetrics.dll shared library. (10363)
Message (excp): com.progress.isq.ipqos.Initialization
Fathom is not installed on the system.
CHANGE:
Installed Progress Service pack 9.1D06 or 9.1D09
CAUSE:
Bug# 20030627-013
FIX:
Upgrade to OpenEdge 10.0A or higher
To workaround the problem disable the SystemPlugin in the AdminServerPlugins.dat file, found in the Progress installation directory. Disabling the SystemPlugin this will cause the osmetrics.dll not to be loaded. Commenting out the Operating System Plugins will not affect the Progress installation. The Operating System Plugins gather system information for Fathom's use. All of the above assumes Fathom is not being loaded onto the system as part of the install.
Disable the SystemPlugin plugin by commenting out this section:
#
# Operating System Plugin
#
#SystemPlugIn
#0
#com.progress.system.SystemPlugIn
#progress.jar
#Operating System Plugin
Start the AdminServer again. It will now start.