Mid Server Down After Cloning! (Login authentication failure)

[saint]

Hi Experts,

ERRORS: 

Login authentication failure for User ldapmidserver associated with down MID Server: 1edd6135479e52905a4564c4f16d4313. Check password on MID server.

MID Server not operational (status: Down), possibly due to recent clone. Verify credentials for logged in User 'ldapmidserver'.

I recently cloned one of my pre-production instances and started encountering these errors. I attempted to resolve the issue by updating the MID Server service account password, but the account continues to get locked out whenever I try to make changes.

From my understanding so far, the account is being locked because the MID Server is continuously polling it for authentication, and the repeated failures are triggering the lockout.

At the moment, I don’t have access to the MID Server machine, as it may require multiple approvals. I’ve read that a possible solution might involve reinstalling or updating the configuration file on the MID Server, or temporarily stopping the polling before changing the password.

I’m unsure how best to proceed from here. Has anyone experienced a similar issue? I would really appreciate any step-by-step guidance on the most effective way to resolve this.

Thank you!

[Dr Atul G- LNG]

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1752300

Resolution

1. Please validate that the user credentials are correct, and update the mid-server user credentials on the affected instances if needed.
2. Unlock the mid-server user on the affected instances.
3. If needed, reset the password for the mid-server user on the affected instances.
4. Restart the affected mid servers on the affected instances.

After performing these steps, the mid servers should be up and running.

**Additional Information:**

Please review the following knowledge base article for more important information on MID Servers and Clones: 
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0786475

[Tanushree Maiti]

Hi @saint 

1. Refer KB: KB0831254 Mid server running but displaying the error "MID Server not operational (status: Down), po... 

Resolution

This is due to the fact that the source MID Server user credentials copied into the target instance might not match those used by the existing set of MID Servers used by the target. You can view the related documentation below:
https://docs.servicenow.com/csh?topicname=mid-post-clone-issue-resolution.html&version=latest

The resolution to this issue would be to perform the below actions:
1) Stop the current MID Server windows service.
2) Go to the MID server /agent/ folder and open the config.xml file with a text editor such as WordPad.
3) Enter the MID user credentials in the mid.instance.username and mid.instance.password parameters.
4) Start the MID Server windows service.

2. Refer KB: KB0786475 MID Servers and Clones 

3. https://www.servicenow.com/community/itom-forum/miduserconnectivity-mid-server-user-issue/m-p/973077...

4. https://www.servicenow.com/community/itom-forum/mid-server-not-operational-status-down-possibly-due-...