MID Server invalid version

Chad31 · ‎02-28-2017

Morning everybody,

I upgraded my dev instance to the latest version of SN and the mid server now puts off a message that says

Reported MID Server version 'istanbul-09-23-2016__patch2-01-11-2017_01-29-2017_2025' is not compatible with instance version '05-26-2016_1303'. Upgrade is required. More Info

so I did my lookup saw various post and still can't figure it out. Its validated, shows up, I don't have a mid.version.override sys property, I did find a mid.version that shows the value of 05-26-2016_1303 but I'm not sure if I do anything with that. Any help is greatly appreciated. Thank you

bennyphipps · ‎03-28-2017

Hi,

I had exactly the same issue and raised a ticket on HI and the response (which appears to have worked) was:

1) Manually changing the mid.version system property to "istanbul-09-23-2016__patch3-02-08-2017_02-24-2017_1059"

2) stop mid server services

3) download the fresh Mid server package from the instance and unzip it.

4) Rename the current installed MID Server "agent" directory to agent_old.

5) Put in the new "agent" directory in the installed MID Server directory.

6) Copy the "config.xml" found in the old "agent" directory and "wrapper_override.conf" file found in the old "agent/conf" directory to the respective directories in the new folder

7) Start the MID Server from the Windows Services.

😎 Validate the mid server if needed

View solution in original post

Darrin Greene · ‎10-25-2023

This definitely helped as I had tried everything else that I knew of, and this fixed my issue and the version is now correct and the MID Server is validated

eddy0042 · ‎10-11-2023

Just in case anyone is coming to this more recently. We're upgrading from tokyo to vancouver and all of our mid servers 'failed' to upgrade.

The resolution was to stop the mid servers and clear the ecc queue ([agentfolder]\work\monitors\ECCSender\) - delete all of the output folders (or move them like I did just incase), then restart the mid server. It seems to take a while to update in the instance (10 mins), and one of ours didn't seem to work until after I re-keyed it and waited another 5 mins although I'm not sure that's strictly necessary.

Good luck

If anyone ServiceNow is on here it doesn't help that the 'info' link on the error on the mid server form takes you to documentation that doesn't exist or has been moved.