Mid Server Not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2012 08:35 PM
Hi,
I have configured a mid server to connect to my service-now instance. i have given proxy address and port number as well. The log file says that MID Server started but it gives the following errors after MID Server started message.
MIDServer MID Server started
11/10/12 09:59:34 (751) StartupSequencer SEVERE *** ERROR *** Problem invoking InstanceInfo on https://company.service-now.com/: IOException: Stream closed
11/10/12 10:00:34 (856) StartupSequencer SEVERE *** ERROR *** Problem invoking InstanceInfo on https://company.service-now.com/: IOException: Stream closed
I was thinking that this could be proxy issue but it is not. I have configured my mozilla to use the same proxy and i am successfully logging into the instance. Anyone has seen this problem before.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-13-2012 01:16 PM
I sometimes get similar errors that i'm still trying to resolve. I also get a 407 error code occasionally. I believe it is definitely a proxy issue. Prior to being migrated to the Gen2 data center all of our traffic went over a VPN tunnel and proxy was not part of the equation. Now that we have been migrated we are going over the public internet for https traffic are we are having these errors on the mid servers.
What I have noticed is that if I get on the server running the MID Server code and open a browser session to the instance that I'm getting the error on then the mid server session will come available and be fine. It seems that the browser causes the session between server and proxy to open up an then all is fine. After logging off the server after a while the proxy session closes and I can no longer connect. There is some timeout that must happen.
I've been trying to get some time with my network engineer to help with this but he has been preoccupied. Once I do and if we find a solution i'll post here. Maybe it will help.
I've also noticed that the issue is more prevalent on my sub-production instances. My production instance loses connection but quickly regains it. I believe this is because the volume of traffic between the mid server and the production instance is greater and also flows in both directions. We use the mid server for event traffic as well so there is where most of the traffic is coming from. I'm running all my mid server instances (7) on one server.
David Pesek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-27-2014 01:58 PM
Hi David, Mohammed
I am facing exactly the same issue. From my home computer I can setup the mid server. But from office network, it doesn't work. However, from the same office server, I can access the service now instance. So I know there is some issue with the network but not able to pinpoint where. ServiceNow log files don't give much help.
Were you able to fix this issue with Proxy/network ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2014 04:28 AM
Hi!
We have the exact same issue as David. After running for around half a day the MID-Server looses the connection to the ServiceNow Instance and won't come back online, restarting the service or the server doesn't help, but opening a browser session to any website instantly brings back the connection?
Anyone any news?
Thanks,
Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-10-2015 01:37 PM
Just had a similar issue - had to setup the Proxy on the conf file.