Mixing Family Releases on MID Servers (Xanadu and Washington)

[Derek Jones]

This morning, we noticed that our two MID servers on a test instance were showing two MID servers as down.  These two MIDs are shared between a few non-prod instances, but the instances are not running the same family releases.  Specifically, the test instance in question is on Xanada Patch 1, and the others are still on Washington Patch 5. Digging further, we noticed this happened after this instance's upgrade to Xanadu Patch 1, leaving the MID on Patch 0.  Also, we're getting "AMB client disconnected after connecting" errors now, which we've not seen before.  

To add to all of this, since the MIDs on the instance are effectively not used (e.g., no active discovery scans, etc.), after trying several different options, the call was to try to uninstall the Xanadu 0 installation and do a new install.  But the installer is kicking up a "user cannot be authenticated or is missing a required role," and this is the same account, with the same roles since New York.  

Is anyone aware of a specific issue with "mixing" MID installs of Xanadu and Washington?  We're basically ready to toss in the towel and clone over this instance, then restart the effort but we'd still be interested in any feedback others have gathered along this same path.  

Thanks!

[Mark Manders]

I think the answer will be 'don't share your MID servers', but I would log a case with NowSupport if I were you. It doesn't sound like such a weird setup that they never dealt with this before. Fact is that a MID Server will upgrade as soon as an instance is upgraded, but it's weird that it stops working if another instance is making use of it.