Notifications

48 views

Description

While installing a new MID server on the MID server host, the installation may fail. Alternatively, the installation may be successful however the MID service does not start. 

We see the below errors in the Wrapper and Agent Logs.

Wrapper log:
2018/10/26 12:06:28 | Launching a JVM...
2018/10/26 12:06:28 | WrapperManager: Initializing...
2018/10/26 12:06:29 | Logger for 'glide' has not been configured by the container, configuring now:
2018/10/26 12:06:29 | Configuring log handler: java.util.logging.FileHandler
2018/10/26 12:06:29 | Setting useParentHandlers=false for Logger 'glide'
2018/10/26 12:06:29 | Overriding formatter to: com.glide.util.DefaultLogFormatter (for handler: java.util.logging.FileHandler)
2018/10/26 12:06:29 | [Fatal Error] :32:78: The reference to entity "JY" must end with the ';' delimiter.
2018/10/26 12:06:30 | ServiceNow MID Server Core service started.
2018/10/26 12:06:31 | <-- Wrapper Stopped

Agent Log:
10/26/18 12:06:28 (978) WrapperStartStopAppMain Running under Java version: 1.8.0_191, java PID: 3488, args: start
10/26/18 12:06:28 (978) WrapperStartStopAppMain Initializing MID Server
10/26/18 12:06:28 (994) MIDServer Creating injector...
10/26/18 12:06:29 (244) MIDServer WARNING *** WARNING *** org.xml.sax.SAXParseException; lineNumber: 32; columnNumber: 78; The reference to entity "JY" must end with the ';' delimiter.
10/26/18 12:06:29 (244) MIDServer Using configuration: C:\ServiceNow\MIDServers\Core_Production\agent\config.xml
10/26/18 12:06:29 (244) MIDServer WARNING *** WARNING *** XPathUtil.selectSingleNode called with null using xpath: //parameter[@name='refresh_rate']
10/26/18 12:06:29 (244) MIDServer WARNING *** WARNING *** XPathUtil.selectSingleNode called with null using xpath: //parameter[@name='instance.date.format']
10/26/18 12:06:29 (244) MIDServer WARNING *** WARNING *** XPathUtil.selectNodes called with null using xpath: //parameter
10/26/18 12:06:29 (244) MIDServer SEVERE *** ERROR *** Unexpected exception, terminating the MID server

Note: The error may be slightly different, however "WARNING *** org.xml.sax.SAXParseException" point to a failure in parsing the configuration file, config.xml.

Release or Environment

Any currently supported Release/Environment.

Cause

  1. Usage of a special character, specifically '&', in the MID user password.
  2. Corrupted config.xml file
  3. Incorrectly formatted config.xml file

Resolution

  1. Test a password without special characters.
  2. Re-create/re-download config.xml and populate parameters again.
  3. Check other software such as chrome or IE can successfully open the config.xml file.
  4. Start the MID service.

Article Information

Last Updated:2020-01-10 12:54:56
Published:2020-01-10