Mid server cannot conect the instance.

Tomoki4
Kilo Contributor

I tried to install a MID Server on Linux in reference to https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/product/mid-server/task/t_InstallAMIDServerOnLinux.html.

I confirmed that the installation was completed correctly, but no record was created on MID Server list.

I checked the log(agent/logs/agent0.log.0) and confirmed the following error.
--------------------------------------------------

10/19/19 02:24:22 (029) StartupSequencer WARNING *** WARNING *** java.net.SocketTimeoutException: connect timed out when posting to https://dev*****.service-now.com/InstanceInfo.do?SOAP
10/19/19 02:24:22 (041) StartupSequencer SEVERE *** ERROR *** SOAP Request: <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://www.service-now.com/GetMIDInfo" xmlns:m="http://www.service-now.com" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"  SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><m:execute></m:execute></SOAP-ENV:Body></SOAP-ENV:Envelope>
10/19/19 02:24:22 (042) StartupSequencer SEVERE *** ERROR *** SOAP Response: Status code=0, Response body=null
10/19/19 02:24:22 (042) StartupSequencer SEVERE *** ERROR *** Problem invoking InstanceInfo on https://dev*****.service-now.com/: Please check that the InstanceInfo page exists in the sys_public table and active="true".
10/19/19 02:24:22 (045) StartupSequencer SEVERE *** ERROR *** java.net.SocketTimeoutException: connect timed out when posting to https://dev*****.service-now.com/InstanceInfo.do?SOAP
(Network Configuration issue) Please check that the MID server can ping the instance: https://dev*****.service-now.com/
You may also need to configure the network that the MID server uses to allow traffic over TCP port 443.
10/19/19 02:24:22 (046) StartupSequencer SEVERE *** ERROR *** test failure
java.lang.IllegalStateException: Unable to connect to instance.
        at com.service_now.mid.services.StartupSequencer.runTests(StartupSequencer.java:455)
        at com.service_now.mid.services.StartupSequencer$Starter.run(StartupSequencer.java:416)

--------------------------------------------------

I focused on  "Please check that the MID server can ping the instance: https://dev*****.service-now.com/".

I use proxy in my environment. It's causing that no ping response to https://*****.service-now.com is returned.
But I think it's no probrem because connection successed at "https://*****.service-now.com" in browser on mid server.(I think it shows 80/443 port connection is no probrem)
 
I'd like to know whether or not mid server cannot conect the instance if no ping response is returned.
1 ACCEPTED SOLUTION

Ankur Bawiskar
Tera Patron
Tera Patron

Hi,

Few things you need to check

1) did you create an user in instance which has mid_server role

2) did you configure the config.xml file properly and update the instance name, mid server username and password

3) is the mid server installed behind a firewall i.e. in private network

4) check the proxy server settings; whether it is not allowing to connect to the instance from the windows mid server service

It might be possible that you can reach a site through browser but may be not through the service which is running for the mid server. I am not 100% sure on this part; but you need to debug further

Mark Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur

 

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

5 REPLIES 5

 

Hi Ankur Bawiskar
Thanks for letting me know.
 
There was the error in this setting of proxy.
I changed the host name to IP.
I changed proxy's host name to IP address. Then, the connection was successfully completed.
 
In your answer, No.4 led to success. Thank you!!