MID Server failed to upgrade - how to resolve this issue

Baskarank
Tera Contributor

In Servicenow MID Server Status is Down and one unresolved issue is MID Server failed to upgrade then Restart the server , after MID Server status is Up but still showing MID Server failed to upgrade  issue , Then after I clicked on the 'Upgrade MID' link and then Restart the server again but still showing this issue, How to resolve this issue?

 

 

Baskarank_0-1737478226773.png

 

6 REPLIES 6

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @Baskarank 

 

Might be helpful

 

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

*************************************************************************************************************
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]

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

AndersBGS
Tera Patron
Tera Patron

Hi @Baskarank ,

 

 have you verified why it fails to upgrade?

 

If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.

Best regards
Anders

Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/

From Agent logs:

2025-01-21 03:41:14 WARN (ECCQueueMonitor.40) [HTTPClient:830]

org.apache.commons.httpclient.ConnectTimeoutException:

The host did not accept the connection within timeout of 10000 ms
2025-01-21 03:41:14 ERROR (ECCQueueMonitor.40) [RemoteGlideRecord:918] getRecords failed

(org.apache.commons.httpclient.ConnectTimeoutException:

The host did not accept the connection within timeout of 10000 ms)

pabjk31
Tera Contributor

For us it was about setting proper username/password - please try at your side?