Kbase P117485: Cannot start AdminServer - Failed to read schema document MFConfigurationElements.xsd
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
OpenEdge Management 3.x
Fathom Management
SYMPTOM(s):
Cannot start AdminServer
AdminServer not alive. (8543)
[AdminServer] Line#:2 Column#:187:schema_reference.4: Failed to read schema document 'file:///<path>/MFConfigurationElements.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>
[AdminServer] Failed to instantiate the management framework container.
[AdminServer] Failed to load the management framework container. (11357)
Remote monitoring with Fathom has been enabled
CAUSE:
The fmconfig was not issued from proenv script but from pure command line window, therefore the Progress AdminServer working directory, listed in the above admserv.log messages where the .xsd file is expected to be copied was not set.
FIX:
1) Ensure that no admsrvc.exe process is running by looking into the Task Manager; if there is one such process, terminate it.
2) find the MFConfigurationElements.xsd on the server and copy it to the AdminServer's working directory.
or in a proenv session, from the AdminServer's working directory, run the following cmd to recreate this file: fmconfig -update -host <host_Fathom_is_running_on>
3) Restart the AdminServer.