Error Upgrading MID Server, Getting "MID upgrade is not supported on 32-bit host" on 64-Bit Host

[Derek Jones]

Recently, I followed up on a few minor errors on a test instance after a patch update to Rome 9 and realized that the MID server was still on Rome 8. Looking at the log, I found that the MID server had failed its pre-upgrade check saying that the host was still running a 32-bit version of Windows and had been failing the assessment for several patches. The odd thing is that both the host and the instances identify the server as 64-bit:

Any "manual" attempt to upgrade the server to the current release from the instance results in a fault and two entries in the Server Issue log, one with an issue source of UpgradeCheck, reporting an aborted install due to the pre-check and a second MIDAssignedPackages complaining about the bit depth.  

Considering the host is running Windows 2012R2 (6.3.9600), I'm inclined to worry about this too much and just request a new VM with a newer OS, but I was curious if anyone else had seen this issue. Honestly, it's more of a curiosity since the server is still up, but I'd like to know what's a fault.  

Thanks

[Ian Mildon]

Weird issue.

We have 9 MID's still running on hosts using Microsoft Windows Server 2012 R2 Standard and they are all using sandiego-12-22-2021__patch4-05-25-2022_06-08-2022_0838

[Derek Jones]

It's not so much as I think 2012R2 is an issue, per se, so much as I'm just left wondering how much time to spend on troubleshooting this versus spinning up new VMs that just happens to come with a newer OS.  But, that said, I get your point.  

[Matt102]

Just a suggestion from someone who know very little of servers - is the MID server installed in 'C:\Program Files (x86)'? Could it be a syswow64 thing?

[Derek Jones]

Actually, for whatever reason, my predecessors installed the client on a separate drive, d:\, which could also be an issue. Maybe the installer has some problem with the "non-OS/C-drive" location? It's worth considering, to be sure.