MID Server DOWN!

Deepanshu Grov1
Tera Contributor

I am trying to configure the mid server, this is showing in DOWN in the ServiceNow dashboard status and when I check the logs, they are following - 

01/31/22 16:40:22 (017) StartupSequencer WARNING *** WARNING *** OCSPCheck HTTP status: 470, error message: Method failed: (/) with code: 470
01/31/22 16:40:22 (017) StartupSequencer WARNING *** WARNING *** OCSP revoke check IOException for *.service-now.com
01/31/22 16:40:22 (017) StartupSequencer WARNING *** WARNING *** Request not sent to uri= https://***.service-now.com/InstanceInfo.do?SOAP : org.apache.commons.httpclient.HttpException: malformed response: unknown object in getInstance: org.bouncycastle.asn1.DLApplicationSpecific
01/31/22 16:40:22 (017) 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>
01/31/22 16:40:22 (017) StartupSequencer SEVERE *** ERROR *** SOAP Response: Status code=0, Response body=null
01/31/22 16:40:22 (017) 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".
01/31/22 16:40:22 (017) StartupSequencer SEVERE *** ERROR *** Request not sent to uri= https://***dev.service-now.com/InstanceInfo.do?SOAP : org.apache.commons.httpclient.HttpException: malformed response: unknown object in getInstance: org.bouncycastle.asn1.DLApplicationSpecific
(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.
01/31/22 16:40:22 (017) StartupSequencer SEVERE *ROFL** ERROR *** test failure
java.lang.IllegalStateException: Unable to connect to instance.
at com.service_now.mid.services.StartupSequencer.runTests(StartupSequencer.java:661)
at com.service_now.mid.services.StartupSequencer.startupSequencerRunnable(StartupSequencer.java:717)
at java.base/java.lang.Thread.run(Thread.java:834)

 

I have checked these all steps, seems no issue, even-though the logs are same. 

10 REPLIES 10

Maik Skoddow
Tera Patron
Tera Patron

Hi

what did you do when saying "I have checked these all steps"? I want to be sure, that you really understood the issue.

Kind regards
Maik

Thank you Maik - Please check my detailed response and advise accordingly - 

  1. Ports from mid server to following sites are opened, I can telnet both the URLs at 443, however, can not ping as ICMP is not allowed in our environment (assuming that it should not make a big difference) as I can load the URLs via server, however, not fully operational.
    1. service-now.com
    2. https://***dev.service-now.com/
  2. Not using any proxy on the server, only above mentioned 2 URLs are accessible and internet is blocked.
  3. Checked scripted SOAP Services, InstanceInfo, it is active.
  4. Checked sys_public and InstanceInfo set to true.
  5. Mid server could not involve SOAP call - https://<instance>.service-now.com/InstanceInfo.do?SOAP , I think this is the issue and not sure how to resolve it now.

VivekSattanatha
Mega Sage
Mega Sage

It seems your MID Server lost connectivity to the instance. Check from the MId Server's IE browser if you can open the Servicenow URL. If you have configured the MID Server with proxy then your browser also should use the same settings.

 

Regards,

Vivek

  1. Ports from mid server to following sites are opened, I can telnet both the URLs at 443, however, can not ping as ICMP is not allowed in our environment (assuming that it should not make a big difference) as I can load the URLs via server, however, not fully operational.
    1. service-now.com
    2. https://***dev.service-now.com/
  2. Not using any proxy on the server, only above mentioned 2 URLs are accessible and internet is blocked.