--- sourceDocument: Yokohama ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/servicenow-platform Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # MID Server pre-upgrade check # MID Server pre-upgrade check {#ariaid-title1} Release version: Yokohama Updated September 21, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of MID Server pre-upgrade check The MID Server pre-upgrade check is an automated validation process that runs prior to upgrading the MID Server. It ensures the upgrade will not fail or cause a MID Server outage by performing mandatory and alert tests. If mandatory tests fail, the upgrade is blocked until issues are resolved. The AutoUpgrade monitor runs hourly to verify if the MID Server version is current and initiates these checks as needed, whether upgrades are manual or triggered by the instance upgrade. Show full answer Show less ## Pre-upgrade Tests The pre-upgrade check consists of two test categories: * **Mandatory tests:** Must all pass for the upgrade to proceed. Failures are logged in the MID Server Issue \[eccagentissue\] table and block the upgrade. These include checks for: * At least 2 GB of free disk space * Access to the ServiceNow download site * Digital signature verification of downloaded files * File permissions for extracting and copying upgrade files * Host system architecture (must not be 32-bit) * glibC version on Linux MID Servers (minimum 2.17) * **Alert tests:** Issues do not block upgrade but generate warnings and log entries. These include: * Running upgrade blocker services on host * Status of Application Experience service * Security best practice warning if MID Server runs under an administrator or LocalSystem account ## Disk Space Checks Disk space is monitored with two thresholds: * **Upgrade-blocking threshold:** If free space is below 4 GB (configurable), upgrade aborts and an issue is logged. * **Warning threshold:** A background monitor checks every 12 hours (default) and logs warnings if free space falls below 36 GB (configurable), regardless of upgrade status. Both thresholds can be disabled via configuration parameters if necessary. ## Common Upgrade Blocking Errors Upgrade is blocked for issues such as: * Insufficient disk space (less than 2 GB free) * Inability to download update packages * Failure to verify digital signatures * Permission issues extracting or writing upgrade files * Unsupported host architecture (32-bit) * glibC too old on Linux hosts ## Non-blocking Warnings Warnings that do not stop upgrades but indicate potential environment issues include: * Improper format or lookup failures for the Windows service Log On As user * PowerShell not available or insufficient version detected (only logged) * Presence of services like CiscoAMP identified as upgrade blockers * Disabled Application Experience service causing potential upgrade failures ## Disabling Pre-upgrade Checks By default, pre-upgrade checks run automatically. To disable: * For a single MID Server, set **mid.upgrade.runprecheck** to **false** in that MID Server's `config.xml`. * For all MID Servers, create a property **mid.upgrade.runprecheck** with value **false** in the MID Server Property \[eccagentproperty\] table. ## Practical Implications for ServiceNow Customers This pre-upgrade check process helps ensure MID Server upgrades are smooth and reliable by proactively detecting common issues related to disk space, permissions, system compatibility, and network connectivity. Customers should monitor the MID Server Issue table for any blocking errors and resolve them before attempting upgrades. Adjusting disk space thresholds and understanding non-blocking warnings can improve operational awareness. Following security best practices, such as running the MID Server under a non-administrator account, is recommended to reduce risk during upgrades. Prior to an upgrade, the MID Server runs tests to identify issues that could cause the upgrade process to fail or result in a MID Server outage. Each MID Server contains an AutoUpgrade monitor that compares the MID Server version with that of the instance to determine if the MID Server needs to upgrade. If the AutoUpgrade monitor discovers that the MID Server version is out of date, the monitor runs pre-upgrade validation tests for that MID Server. If an issue is detected, a message is logged to the MID Server Issue \[ecc_agent_issue\] table, and the upgrade is blocked. The AutoUpgrade monitor continues to run every hour, until all the tests pass. If there are no blocking issues, the MID Server downloads the appropriate upgrade package and begins the upgrade process. The MID Server pre-upgrade check also runs for the upgrades triggered by the instance when the instance was upgraded, as well as for manual upgrades. ## Pre-upgrade tests {#mid-server-pre-upgrade-check__section_xnl_vr1_fqb} The pre-upgrade runs two sets of tests: Mandatory tests and Alert tests. Every mandatory test is required to pass to start MID Server upgrade. If a mandatory test was not passed, the test is recorded in the agent log and a [MID Server active issue](https://www.servicenow.com/docs/1dq1v31cxecby_AP2FmS3w "The ServiceNow instance has a dedicated table that publishes active issues with MID Servers and alerts administrators when a MID Server is in danger of exceeding its resources.") is created in the MID Server issue \[ecc_agent_issue\] table. These errors are published before the actual MID Server upgrade occurs and must be resolved before the upgrade can continue. MID Server stops the Upgrade process and changes the status based on [MID Server states](https://www.servicenow.com/docs/0fmzqDHt0iEzymIrRBjJUA#c_UpgradeAndTestMIDServer__section_t1p_jc4_1qb). If any alert test was not passed, a message is added in the agent log and MID Server issue table. However, the pre-upgrade check continues and MID Upgrade doesn't stop. Pre-upgrade validation tests check the following mandatory tests: * At least 2 GB of free disk space * Access to the download site at install.service-now.com * Verify the digital signature of a sample downloaded file * Permission to execute, which involves the following: * Extract a Zip archiver to the upgrade temp folder: agent/work/upgrade_temp * Copy files from the upgrade temp folder to the agent folder * Read a text file and validate the content * Delete the pre-upgrade check contents {#mid-server-pre-upgrade-check__ul_b4m_zs1_fqb} * MID Server host machine is not a 32 bit system * On Linux MID Servers, the glibC version is at least 2.17 {#mid-server-pre-upgrade-check__ul_lj5_ws1_fqb} On Windows MID Servers, the pre-upgrade validation runs the following alert tests: * Any MID Server Upgrade blocker services is running on the host machine * Status of Application Experience on the host machine * For security best practice, run the MID Server as a non-administrator user. If the current Log On As user account for the MID Server is LocalSystem or is a user that is part of the Administrators group, the upgrade does not fail. However, this configuration is not recommended. {#mid-server-pre-upgrade-check__ul_hbw_2t1_fqb} ## Disk-space checks {#mid-server-pre-upgrade-check__section_ets_1c5_nkc} The MID Server needs sufficient free disk space to perform upgrades and run reliably. The MID Server monitors available disk space and alerts administrators before low disk space disrupts MID Server operations. The MID Server performs two disk-space checks: an upgrade-blocking threshold and a warning threshold check.{#mid-server-pre-upgrade-check__section_ets_1c5_nkc-para-1} Upgrade-blocking threshold check: : If free space is below the mid.upgrade.min_disk_space_gb configuration parameter value (default is 4 GB) when an upgrade begins, the upgrade aborts. An issue record is created on the instance. Warning threshold check: : A background monitor named `DiskSpaceCheckMonitor` runs at MID Server startup and then every mid.disk_space_check.interval hours (default is 12 hours). Changing this configuration parameter requires a MID Server restart to take effect. If free space is below the mid.disk_space_check.low_space_warning_threshold_gb configuration parameter value (default is 36 GB), the MID Server logs a warning and creates an issue record. It does this whether or not an upgrade is in progress. The MID Server writes issue records with the same source, `DiskSpaceCheck`, for both checks, so it updates a single issue record. When free space returns above the warning threshold, the MID Server resolves the issue record automatically on the next check. The MID Server creates no issue records when free space stays above the thresholds.{#mid-server-pre-upgrade-check__section_ets_1c5_nkc-para-2} To disable the upgrade-blocking check, set mid.upgrade.min_disk_space_gb to 0. To disable the warning threshold check, set mid.disk_space_check.low_space_warning_threshold_gb to 0.{#mid-server-pre-upgrade-check__section_ets_1c5_nkc-para-3} ## Errors that block the upgrade {#mid-server-pre-upgrade-check__section_cdl_3t1_fqb} These messages describe failing a mandatory test and are published to the MID Server Issue \[ecc_agent_issue\] table. Failure of any of these tests blocks the upgrade. Not enough free disk space. The system reports \ bytes free : This message is displayed when less than 2 GB of free disk space is detected on the MID Server host. This error is also written to the MID Server agent log. Unable to download updates from the install server : This message indicates that either the MID Server host does not have permission to download the installation package from install.service-now.com, or network problems prevent connection. This error is also written to the MID Server agent log. Signature verification failed:\ : This message indicates that a Verification Exception has occurred when pre-upgrade check tries to verify the digital signature of the downloaded check file. Unable to verify digital signature:\ : This message indicates that the verification signature process was interrupted by an exception. Unable to extract contents of pre upgrade check zip : This message indicates that the service account on the MID Server host does not have permission to extract the pre-upgrade ZIP archive to the temporary folder. Unable to create folder \ : This message indicates that the MID Server service account does not have permission to create the upgradeCheck folder for the pre-upgrade checking files in the agent/package path. Unable to verify file permissions: \ : This message indicates an exception has occurred when checking file permissions, such as a file that does not exist or access failure. The MID Server Windows service runs as LocalSystem or a user that is part of the Administrators group. : This message warns that the Windows service is running with elevated privileges, which increases the risk of unintended access or actions. Upgrade Failure: The host machine does not meet the minimum system requirements to upgrade the MID server. : MID upgrade is not supported on 32-bit host. Please refer to [KB0863694](https://support.servicenow.com/nav_to.do?uri=/kb?id=kb_article_view&sysparm_article=KB0863694) for more information. Upgrade Failure: Host does not meet the minimum system requirements to upgrade the MID server. Please refer to MID Server product documentation on GlibC library for more information : This error can only occur for Linux MID Servers. Refer to [Java version support](https://www.servicenow.com/docs/4j~DXw_Cfdj1uyhyC10Muw "Use these minimum system requirements to allocate resources for computers hosting MID Servers.") for more information. ## Non-blocking warnings {#mid-server-pre-upgrade-check__section_grh_g51_fqb} These warnings are displayed in the MID Server Issue \[ecc_agent_issue\] table and do not prevent a Windows MID Server from upgrading: Unable to parse $logOnAsUser : This message warns that the Log On As User value for the Windows service is not in either of these expected formats: * user@domain.company.com * domain\\user {#mid-server-pre-upgrade-check__ul_abl_351_fqb} Unable to look up Log On As user's groups : When the instance attempts to look up the logged on user's group memberships, it executes the net user \ command. The instance expects a certain output structure by the Windows service from this command and issues this warning if the expected output does not match the actual output. These PowerShell warnings are written only to the MID Server agent log. Because PowerShell is not required to use a MID Server, these configuration issues do not prevent a Windows MID Server from upgrading. However, these warnings might indicate issues in your environment that require attention. Skipping PowerShell upgrade checks since PowerShell is not usable : PowerShell 3.0 (at a minimum) is not installed or powershell.exe is not available to the MID Server service user. Skipping Powershell test: Target folder has not been initialized : Skipping Powershell test: Unable to detect the service name : Service CiscoAMP running on the MID Server host machine is identified as a MID Server upgrade blocker : For more information, refer to [KB0870329](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0870329). The Application Experience is disabled on the MID Server host, which can cause the auto-upgrade process to fail and the MID Server to go down. Enable the service on the host to ensure successful auto-upgrade : For more information, refer to [KB0597552](https://support.servicenow.com/kb_view.do?sysparm_article=KB0597552#appex&_ga=2.137899701.402632408.1615226320-1555493315.1610383440). Continuing with upgrade, but the following issue was encountered during upgradeCheck: \ : This message indicates that there was an issue running the PowerShell portion of the pre-upgrade tests. ## Disabling the pre-upgrade check {#mid-server-pre-upgrade-check__section_by4_w51_fqb} A MID Server configuration parameter called mid.upgrade.run_precheck is set to true by default, which allows the automatic pre-upgrade test to run. To disable these tests for a single MID Server, add this parameter to that MID Server's config.xml file and set it to false. To disable these tests for all MID Servers, add a new record to the MID Server Property \[ecc_agent_property\] table called mid.upgrade.run_precheck. Set the value of this property to false and leave the MID Server field blank.