MID server shows version mismatch

[RavishShett]

Hi all,

We installed MID servers recently and it seems there is version mismatch between the MID server version and the instance version. Probably because we used MID server installer files from another ServiceNow instance. I opened these MID server records in the ecc_agent table and clicked on the 'Upgrade MID' related link, but nothing happens after the status briefly showing 'Upgrading'. I tried it a few times. What can we do here?

Thanks,

Ravish

[pr8172510]

Hi @RavishShett,

A version mismatch is expected if the MID Server was installed using binaries from a different instance. Normally, the MID Server should automatically upgrade to match the instance version.

Since the Upgrade MID action is not completing
check

• agent0.log.0 for AutoUpgrade messages and pre-check failures.

• wrapper.log for upgrade or service restart errors.

• Ensure the MID Server is not pinned (mid.pinned.version or mid.version.override).

• Verify the MID Server can reach install.service-now.com over HTTPS (port 443).

• Confirm the MID Server service account has permission to update the MID Server installation directory.

If the auto-upgrade continues to fail after resolving any pre-check or connectivity issues, reinstall the MID Server using the installer downloaded from the target ServiceNow instance.

[Vinayak2443]

Using installers from another instance is a common cause of version mismatches. Since the version mismatch stems from using the wrong installer, the most reliable fix is a manual reinstall rather than relying on the auto-upgrade button. Download the correct MID server installer directly from your instance.

Please refer the KB from the link below.
MID Server version compatibility - Support and Troubleshooting

[Vinayak2443]

Since the version mismatch stems from using the wrong installer, the most reliable fix is a manual reinstall rather than relying on the auto-upgrade button. Download the correct MID server installer directly from your instance