The Mid Server did not upgrade Error " reported mid server version 'newyork-06-26-2019__patch9a-06-24-2020_08-10-2020_1624' is not compatible with instance version 'paris-06-24-2020__patch1-hotfix3-09-23-2020_09-24-2020_1618'.

[rontha]

Recently upgraded from New York patch 9a to Paris Patch 1 hotfix3. But the mid Server didn't get upgrade. Error below

Reported mid server version 'newyork-06-26-2019__patch9a-06-24-2020_08-10-2020_1624' is not compatible with instance version 'paris-06-24-2020__patch1-hotfix3-09-23-2020_09-24-2020_1618'.

[Prashanth Kuma4 · Accepted solution]

Hi,

This error will be shown when the your instance is upgraded and not matching the MID server version. Ideally the MID server should auto upgrade. But in your case it didn't.
To fix this, open MID server record in your instance and manually click on upgrade.

OR

If the MID server is down

1. Login to server
2. WIN + R
3. services.msc
4. Start MID service

[rontha]

Thanks Prashanth.

MID server was down, 

After restarting the Mid Service, the Mid Server got updated to New Paris Version.

Thanks

Rontha

[Hitoshi Ozawa]

Following page contains information on failed MID Server upgrade. It has information such as when the upgrade will fail as well as how to resolve the issue.

For example, automatic upgrade on Windows computer will fail is Windows Application Experience is disable, access to OCSP is blocked, there is not enough free disk space, service is not running as LocalSystem or local Administrator.

To manually perform an upgrade, mid_server or admin role is required. MID server must be in up state and must be validated. Any error detected in pre-update test must be resolved before upgrade is executed.

https://docs.servicenow.com/bundle/paris-servicenow-platform/page/product/mid-server/concept/c_Upgra...