Mid Server User account locked out
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2022 07:25 AM
Hi All,
We have cloned our TEST instance to Tokyo and our mid servers need to be upgraded. I see the Mid User account is locked out and I am unable to unlock it. Mid server services are running in host machine but in SNOW it is showing status as down.
Tried resetting the password in config xml but still the account is not unlocked.
Can anyone help me with this?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2022 08:06 AM
Hi, why you cannot unlock the user? What error do you see when try to unlock it?
You need to unlock the user in ServiceNow instance. Changing the password in config.xml should not help there.
Hope it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2022 08:38 AM
Hi Appli,
Even though I uncheck the locked out value and saved the form it is again showing the same when I refreshed it.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2022 09:19 AM
Hi,
There can be numerous reasons. For instance, mid server account being used some where else & is trying to authenticate. Adding few links that should help you drill the issue.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0597574
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2024 09:05 AM
Ah, yes, I had this issue after a recent clonedown as well.
I worked around it by temporarily adding a character to the user_name value on my MID user record. After doing that, I unlocked and reactivated the account, reset the password, then used /login.do in a private browser window to login to the account and change the password to what I had set up on my TEST instance MID Server.
Finally, I changed the user_name back to what it was supposed to be, and everything started working again.