After every patch upgrade MID Server is getting down, How can we resolve it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 04:32 AM
Hola,
After every patch upgrade or instance upgrade, Is it normal Mid Server getting down? Is there any way we can automate the process of configuration at the server side? How can we know reason behind MID is down? Due to mid server down, LDAP is getting affected.
Thanks
Prince

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 04:46 AM
Hello,
We used to get this issue in the past and I think we did upgrade of mid servers and it resolves the issue. I don't recall exactly about entire solution as we faced this issue more than 5 years back. I suggest you create HI ticket with ServiceNow team and they will suggest you the solution.
Regards,
Musab
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 06:43 AM
Do you know the root cause?
In washigton their was a patch if someone has installed that it was falling to upgrade.
Apart from that if mid server have access to install folder on service-now it should be able to do the upgrade.
If non prod environment failing after clone then go for same users in all the instance ( please note as per new guideline by servicenow if you have three mid servers then all the mid servers should have different mid server users)
If you see the mid server issue it will going to tell you what might have gone wrong. Mid server logs can help to get the root cause. I would suggest to do the root cause analysis and add that to pre and post update task for the instance.