- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2025 06:34 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2025 06:38 AM
Cause:
There are many causes for MID Server validation issues. However, one of them could be when installing a new MID Server, you have copied the /keystore folder from an existing installation.
Resolution :
If you encounter this issue and have tried to rekey your new MID Server, remove the /agent/keystore folder and restart the MID Server. Upon restarting, the /keystore folder will be recreated.
You should then see the MID Server in an UP state and Not Validated. At this point, you can validate the MID Server.
If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!
Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI
ï”— YouTube: https://www.youtube.com/@learnservicenowwithravi
ï”— LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2025 11:16 PM
Did you get a chance to review this ?
If my response helped to answer your query, please mark it helpful & accept the solution. As per community guidelines, you can accept more than one response as accepted solution.
Thanks,
Bhuvan