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

Chuck Tomasi · ‎02-28-2017

My recommendation is to keep your config files, remove the MID server installation, and download the MID server software directly from the instance that was upgraded. That will ensure both match.

http://wiki.servicenow.com/index.php?title=MID_Server_Installation

Chad31 · ‎02-28-2017

Thank you for the quick response.

Please forgive my lack of understanding on this, I wasn't the one to setup the mid server on my instance and that person is not reachable.

Do I need to uninstall the old version on the mid server first? Then just follow the ITOM guided setup to do this. I am reading through the link that you sent now but wasn't sure about the uninstall piece.

Chuck Tomasi · ‎02-28-2017

Sorry for the confusion.

Yes, uninstall the software from the Windows or Linux server where the MID server agent is running. Delete the record on the instance that indicates the status of the MID server. That should reset you back to 'factory defaults' and allow you to do a clean installation/configuration where both versions match.

Chad31 · ‎02-28-2017

Last question, are the versions backwards compatible? For instance IF (and I dont know if this holds true at this exact moment) the dev instance uses the same MID server as the PROD instance will it affect prod at all by updated the version?