MID Server invalid version

[Chad31]

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

[Chuck Tomasi]

Hi Chad,

For best results, the MID server and the instance it communicates with should be matching versions. If you upgrade the instance software, upgrade the MID server software at the same time. If they get out of sync you can have unpredictable results.

[Chad31]

Hey Chuck,

So I uninstalled the service from our mid server, downloaded the upgrade from the instance Copied over the config file , ran the start.bat script from the directory in an elevated command prompt and everything looked good mid server wise.

In my dev instance I still get the same message.

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

I looked for where it was getting that value from and it see a sys property called mid.version type is string and value is '05-26-2016_1303' does that have anything to do with this or is that something that updates automatically?

Any other suggestions?

[Chad31]

So as a test I changed the mid.version sys property to istanbul-09-23-2016__patch2-01-11-2017_01-29-2017_2025 and everything looks fine now, shows green for the mid server everything looks good.

Is it ok to change that property, my thought is that the person who set all this up was controlling the version with that and instead of calling it mid.override.version she called it mid.version. Just not sure if I needed to do that or not.

[Chuck Tomasi]

Hi Chad,

As a best practice, I wouldn't mess with that property. I wouldn't be surprised if it changes back as well when the MID server checks for an upgrade status check periodically. I don't know specifically how that property is maintained. It sounds like you found a workaround, but be diligent about keeping the instance and MID server in sync going forward.

Thanks for sharing.

[bennyphipps · Accepted solution]

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