
- 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
‎07-07-2020 06:16 PM
Faced same issue then I followed your instructions and it worked like a gem. But I had to stop the mid server first and then start again from cmd prompt.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-15-2020 08:00 AM
The solution I found with Orlando release was close to @Esmond's - in my case I had to run the install batch file in the bin folder first (AFTER running the installer). So for example:
1. C:\SNOW MID\agent\bin and double click on InstallMID-NT batch file.
2. C:\SNOW MID\agent\bin and double click on StartMID-NT batch file.
Those steps caused my new mid server service to show up on the server itself, and to show up on the instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2020 10:42 PM
Follow the same procedure for New York as well 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-03-2020 09:13 PM
It worked yeah.