How to convert a 32bit MID server install to 64bit by replacing the JRE - Support and Troubleshooting

How to convert a 32bit MID server install to 64bit by replacing the JRE Summary Until the Dublin (2015) release, although 64bit editions of Windows Server and Linux were standard, ServiceNow only had a 32bit installer for MID Server, which contained a 32bit version of Java Runtime Environment (JRE). As with any 32 bit application this limits the maximum memory for the process to 2GB, and so to be able to increase the Java heap space, a 64bit installer was created.

However, all 32bit installs would have remained 32bit to this day (Rome), being auto-upgraded with a newer 32bit JRE each time.

There are reasons to want to change this to 64bit:

Allow increasing the Java heap space, when the features you run in the MID Server cause out-of-memory errors. e.g. big Discovery Patterns, huge Import Sets. All new installs will be 64bit, and supporting them is easier when they are standardised. To allow auto-upgrade in Rome to work without turning off the pre-upgrade checks, which can break because of known problem PRB1548158: See KB1001926 - 32 Bit MID Server installed on 64 Bit host machine fails AutoUpgrade in Rome Release Has become more of an issue since Rome.

Instructions Here are the steps to move to a 64bit JRE, without needing to re-install the MID Server:

Confirm the install is the 32bit JRE by opening agent\package\meta\mid-jre.meta.properties in a text editor. If the package.filename value ends ...x86-32.zip then the MID Server install is using the 32bit JRE. Stop the MID Server windows service Back up the cacerts file , which contains any self-signed root CA certificates you may have added, by copying the cacerts file to a safe place, outside of the jre folder: agent\jre\lib\security\ cacerts . Delete the jre folder : \jre Delete the mid-jre.meta.properties file : agent\package\meta\mid-jre.meta.properties Download the JRE 64bit package* , and extract to a temporary folder. See below for finding URLs for different versions/platforms. Cut the "jre" and "package" folders from within the extracted files in the temp folder. Paste them in your MID Server installation's agent\ folder . Restore your cacerts backup to agent\jre\lib\security\cacerts, overwriting the file Start the MID Server service. If you are on Rome, change the state of the "MIDAssignedPackages" MID Server Issues record to "Resolved". * Finding the right URL for Downloading the JRE ZIP file specific to your Instance Version/Host Server Architecture The JRE version is normally only changed with major instance versions, however that's not guaranteed due to security patching requirements. It is best to download the zip file specific to the instance version.

Attached to this KB article is a spreadsheet that will list all the URLs for all the ZIP files for a specific instance version, a.k.a. "MID Buildstamp".

To find your instance MID Buildstamp, open the /stats.do page, and the MID Buildstamp is in the top section. It will look like this, but not be the same value as this example:

https:// .service-now.com/stats.do ... MID buildstamp: sandiego-12-22-2021__patch0-01-19-2022_01-22-2022_2230 ... The rows highlighted in this screenshot are the URLs you will need, depending on Linux or Windows:

Related Links The Windows Service does not need recreating, because it runs a Tanuki wrapper executable, which has always (since at least Calgary) been the version of the executable matching the host architecture. Both 32bit and 64bit installs will be executing wrapper-windows-x86-64.exe on a Windows host, and so the service command does not need changing.

If you have trouble with the attached spreadsheet, you will probably be OK with these links:

New York, Orlando, Paris: (1.8.0_231)

Windows x86-64 mid-jre.newyork-06-26-2019__patch8-04-01-2020_04-10-2020_1401.windows.x86-64.zip Linux x86-64 mid-jre.newyork-06-26-2019__patch8-04-01-2020_04-10-2020_1401.linux.x86-64.zip Quebec: (11.0.8)

Windows x86-64 mid-jre.quebec-12-09-2020__patch1-02-18-2021_03-01-2021_1225.windows.x86-64.zip Linux x86-64 mid-jre.quebec-12-09-2020__patch1-02-18-2021_03-01-2021_1225.linux.x86-64.zip Rome: (11.0.9.1)

Windows x86-64 mid-jre.rome-06-23-2021__patch6-01-13-2022_01-18-2022_0138.windows.x86-64.zip Linux x86-64 mid-jre.rome-06-23-2021__patch6-01-13-2022_01-18-2022_0138.linux.x86-64.zip San Diego: (11.0.12)

Windows x86-64 mid-jre.sandiego-12-22-2021__patch0-hotfix2-02-04-2022_02-07-2022_1650.windows.x86-64.zip Linux x86-64 mid-jre.sandiego-12-22-2021__patch0-hotfix2-02-04-2022_02-07-2022_1650.linux.x86-64.zip