- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2019 02:10 AM
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.
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/".
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2019 02:10 AM
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
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2019 05:33 PM