MID Server not able to install

kms
Kilo Expert

Hi All,

I am trying to install MID Server for discovery. I have downloaded the MID Server from service now and installed in the system. Also followed the steps given in Service now and made changes in config.xml and wrapprer.override.xml. I am able to see the MID Server service created in services. But not able to start.

Please help me on this issue

1 ACCEPTED SOLUTION

Antony_Alldis
ServiceNow Employee
ServiceNow Employee

Hi Shyama,



This is sounding like a configuration issue in the <path_to_MIDserver>\agent\config.xml



07/25/16 05:59:34 (157) MIDServer WARNING *** WARNING *** org.xml.sax.SAXParseException; lineNumber: 30; columnNumber: 79; The entity name must immediately follow the '&' in the entity reference.



Please check line 30 - column 79 of the config.xml file - I would hazard a guess this will be the "password" parameter.



To resolve it - use a password that doesn't contain an ampersand "&" as this appears to be breaking the XML.



Regards,



Tony


View solution in original post

13 REPLIES 13

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

Hi Shyama,



You may find below video helpful.


Troubleshooting ServiceNow MID Server Issues - YouTube


Antony_Alldis
ServiceNow Employee
ServiceNow Employee

Hi Shyama,



If the Service has started, then the place to look is in the agent log to explain what is happening.



This is normally called: <path_to_MIDserver>\agent\logs\agent0.log.0



If this is a new MID server - ensure that the MID server user on the instance, has:



A) Been created


B) Is unlocked


C) Has the correct password applied


D) Has the mid_server role applied to the account



Regards,


Tony


Hi Tony,



The service is not started. I am not able to start that.



If I try to start it is automatically getting stopped in 2 seconds


Antony_Alldis
ServiceNow Employee
ServiceNow Employee

Hi Shyama,



If the Service is not starting then you need to look at the following log file:



<path_to_MIDserver>\agent\logs\wrapper.log



This contains the information pertinent to the "Service" (i.e. the JVM).



As Dan has already suggested, ensure that this is running under a Local/Domain Admin account i.e. the recommended type of Accounts to run a MID server.



My recommendation would be:



Open a PowerShell Window (*as an Administrator)


CD to <path_to_MIDserver>\agent\


.\stop.bat


.\start.bat



Note if there are any errors on startup.


Check the wrapper.log for errors.



If the log has errors in it, then please inform us what they are.



Thanks.


Tony.