
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-27-2018 12:21 PM
Dear all,
I have a new MID server installation. The MID server installed and connected successfully. No error in log what so ever.
I see hartbeat of the MID server comming as well.
But it's never shown in MID servers list. I checked KBs related to the issue, but can't find a problem.
What troubleshooting steps should I take?
Dmitry
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2018 05:44 AM
I got an answer from the support. This is a Jakarta specific defect.
This issue has been fixed in our Kingston and Jakarta Patch 10 release, so please upgrade the instance and then this issue will not occur.
If you cannot upgrade to Kingston then the below workarounds could be used:
- Use a pre-Jakarta Patch 9 installer instead, which will work, and then it will immediately upgrade itself to match the instance version.
Links to Jakarta Patch 8c Installer ZIPs: Windows: 32 bit, 64 bit, Linux: 32 bit, 64 bit - Install a new MID Server using the Jakarta Patch 9 installer from your instance MID Server Downloads page, by following the manual installation steps as outlined below:

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2018 05:34 AM
Hi,
Its some unique issue which I have seen for some customers. I dont know its a bug in a particular version.
For us it worked after we configure config file manually. We copied config file from other working MID server and configured manually.
Regards,
Vivek

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2018 05:44 AM
I got an answer from the support. This is a Jakarta specific defect.
This issue has been fixed in our Kingston and Jakarta Patch 10 release, so please upgrade the instance and then this issue will not occur.
If you cannot upgrade to Kingston then the below workarounds could be used:
- Use a pre-Jakarta Patch 9 installer instead, which will work, and then it will immediately upgrade itself to match the instance version.
Links to Jakarta Patch 8c Installer ZIPs: Windows: 32 bit, 64 bit, Linux: 32 bit, 64 bit - Install a new MID Server using the Jakarta Patch 9 installer from your instance MID Server Downloads page, by following the manual installation steps as outlined below:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-26-2020 11:56 PM
i am facing same issue in ORLANDO , tried your way of installing jakarta , its showing after istalling jakarta but thats not upgrading

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2020 08:24 AM
I have faced the same issue with Orlando release, where I tried everything but still the mid server didn't show up on my instance. Removed the entire MID server Orlando installation package from the windows server and installed the MID server application compatible with the NewYork release (mid.newyork-06-26-2019__patch4-hotfix1-12-16-20...). Followed the same installation procedure and this time it showed up in the list of my MIDServer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-10-2020 03:55 AM
For Orlando release, after installation, you need to go to your extracted MID Server folder, for example; C:\SNOW MID\agent\bin and double click on StartMID-NT batch file.
This will then start the MID Server service in the Windows Server and now you can view this in your list of MID Servers in ServiceNow.