- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-10-2025 03:53 AM
Hello
I see this message for a MID server
Reported MID Server version 'washington-__patch4b-08-2021_1058' differs from instance version 'washington-patch10b-10-220_1502' though they are compatible. Upgrade is recommended. More Info
The hyper links takes me no where.
Couldnt find any community post or knowledge article with that error message (found similar not exact one).
Tried clicking on 'Upgrade MID' ui action, happened. Same message is showing up.
Any idea for this fix?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2025 12:36 AM
ServiceNow support team also couldnt find out the rootcause. We went with reinstallation of MID server.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-20-2025 07:38 PM
If it says compatible means they are in the same family just different version then just restart the MID server will solve the issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2025 12:01 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-20-2025 11:02 PM
Hello @Suggy
Restart and Validate the Mid server. It is because they are of same Release but different versions that this is happening
You can use the Batch files within your mind server to avoid any mishaps.
Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwN
eEISQCY.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2025 12:36 AM
ServiceNow support team also couldnt find out the rootcause. We went with reinstallation of MID server.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2025 12:56 AM
Hi Suggy,
The different version can be solved by just restarting the MID server from the host, I've done that to many servers and it worked.