Installed MID server but I'm getting a "duplicate name" error in the logs and the MID won't work

[tspitalnick]

I have a new, clean London dev instance and downloaded the mid, set up the install and it worked just fine. I gave my MID a totally unique name and it's logging in via my admin credential (I know, I know, but it's just a dev instance). I do the startup, the MID shows up in my instance, I validate, but then I get this:


10/30/18 09:14:51 (244) StartupSequencer WARNING *** WARNING *** Encountered error: [An active MID Server with a duplicate name detected.] in ensuring agent record on the instance. Retry...
10/30/18 09:14:51 (244) StartupSequencer Waiting to retry in 5 minutes. Attempt 1 of 3.
10/30/18 09:19:51 (879) StartupSequencer WARNING *** WARNING *** Encountered error: [An active MID Server with a duplicate name detected.] in ensuring agent record on the instance. Retry...
10/30/18 09:19:51 (880) StartupSequencer Waiting to retry in 5 minutes. Attempt 2 of 3.
10/30/18 09:24:52 (486) StartupSequencer WARNING *** WARNING *** Encountered error: [An active MID Server with a duplicate name detected.] in ensuring agent record on the instance. Retry...
10/30/18 09:24:52 (486) StartupSequencer Waiting to retry in 5 minutes. Attempt 3 of 3.

10/30/18 09:29:54 (424) StartupSequencer WARNING *** WARNING *** Encountered error: [An active MID Server with a duplicate name detected.] in ensuring agent record on the instance. Retry...
10/30/18 09:29:55 (210) StartupSequencer Stopping MID Server due to exceeding retry attempts.

Then it shuts down for good. I absolutely do not have another MID by the same name. I DO have another mid that still exists from a prior install, but it is confirmed that the service is inactive and definitely a different name.

Any ideas?

Edit: In the MID unresolved issues, this came up: "A MID Server with a duplicate name or sys_id was prevented from connecting. Install path: C:\agent-london. This issue must be manually resolved."

[Joe Romeo]

This was the answer for us as well. We added an extra layer of folders with unique names (MID1 and MID2) and moved the installation into them. It's silly, but it worked.

[Hiroko2]

Hell.

I also experienced the same problems, and I success to validate MID Server by changing the JDK version.

[NG]
 jdk-11.0.2 + jre1.8.0_201
 *Encountered error: [An active MID Server with a duplicate name detected.] in ensuring agent record on the instance.

[OK]
 jdk1.8.0_201 + jre1.8.0_201