We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

MID server shows version mismatch

RavishShett
Tera Contributor

2 weeks ago

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?

 

RavishShett_0-1782418700464.png

 

Thanks,

Ravish

0 Helpfuls
  • 1,202 Views
5 REPLIES 5

pr8172510
Kilo Sage

2 weeks ago

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.

 

0 Helpfuls