Unable to Validate the Mid-Server !!

SandeepKSingh · ‎08-24-2025

The image shows the error!!

Ravi Gaurav · ‎08-24-2025

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/

View solution in original post

Ravi Gaurav · ‎08-24-2025

Hi @SandeepKSingh

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/

SandeepKSingh · ‎08-24-2025

Hi @Ravi Gaurav
truly Appreciate!!.. how you have this much of knowledge.. Thanks for quick help on Weekends

Shashank_Jain · ‎08-24-2025

Hello @SandeepKSingh ,

If you see “MID Server validation failed, please try rekey”, it usually means the keystore is corrupted.

Stop the MID Server service.
Delete/rename the keystore folder (e.g., agent/keystore).
Restart the MID Server (this creates a fresh keystore).
From the MID Server record in ServiceNow, click Validate/Rekey.

Hope it helps!

If this works, please mark it as helpful/accepted — it keeps me motivated and helps others find solutions.
Shashank Jain

Bhuvan · ‎08-24-2025

@SandeepKSingh

Refer below knowledge article,

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

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 this helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan