
- 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-27-2018 02:21 PM
Please restart your mid server to see if this resolves your issue.
Also, did you installed supported mid server version for your instance version?
Regards.
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-27-2018 02:25 PM
Check your config.xml to make sure it's pointing at the same instance you're looking at.
(Been there. Done that.)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-27-2018 04:09 PM
Check the agent and wrapper logs (MID Server folder >> agent >> logs) this gives more details. Mostly related proxy/username pwd issues. Also check if the MID Server user have proper roles.
Thanks,
Giri Guntoju

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2018 07:35 AM
Thank you, guys.
MID server was restarted multiple times.
The instance it connects to is an instance I'm looking at. I could see a heartbeat from the MID server, so it's a right one.
Agent0.log.0 is free from errors and showing a proper connection to the instance.
User has all required roles.
How could I see records in ecc_agents?