Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

MID Server is stuck in Validating state

RoseF1235
Tera Contributor

Troubleshooting steps perfomed

  1. Stopped the MID Server service.

  2. Removed the encrypted key from the MID Server configuration.

  3. Cleared security files located in both the security and security_backup folders.

  4. Restarted the MID Server service.

  5. Invalidated and attempted to re-validate the MID Server from ServiceNow.

4 REPLIES 4

Dr Atul G- LNG
Tera Patron
Tera Patron

HI @RoseF1235 

If this is a lab instance, then try again — log out and log back in. Sometimes it gets stuck.”

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

This is in the dev environment @Dr Atul G- LNG 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0696701  @RoseF1235 

 

https://www.servicenow.com/community/developer-forum/mid-sever-status-is-in-validating/m-p/2535428

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

kaushal_snow
Giga Sage

@RoseF1235 ,

 

Often it happens because of time or timezone mismatches between the mid server host and the ServiceNow instance.... if the server clock/timezone doesn’t match, the validation may never complete.....Another frequent issue (especially on Linux/Ubuntu installs) is a corrupted or out of sync keystore: deleting the agent_keystore (or the keystore file under the agent security folder) and then restarting/re validating sometimes resolves the issue......If the MID Server runs under a non default user (especially on windows), you must ensure that user is listed in the mid.windows_host.file_permissions.allow_list in config.xml.... incorrect file system permissions often block validation.......

 

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

 

Thanks and Regards,
Kaushal Kumar Jha - ServiceNow Consultant - Lets connect on Linkedin: https://www.linkedin.com/in/kaushalkrjha/