MID Server Download or Upgrade Returns 404 Not Found in Regulated Market Environments (GCC, NSC, NIPRNet) - Support and Troubleshooting

MID Server Download or Upgrade Returns 404 Not Found in Regulated Market Environments (GCC, NSC, NIPRNet) .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: 'Lato', sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; max-width: 100%; } .kb-wrapper h2 { font-family: 'Lato', sans-serif; font-size: 14pt; font-weight: 900; color: #032D42; border-bottom: 2px solid #e8fce4; padding-bottom: 4px; margin-top: 24px; margin-bottom: 10px; } .kb-wrapper p, .kb-wrapper li { font-family: 'Lato', sans-serif; font-size: 12pt; line-height: 1.7; margin: 6px 0; } .kb-wrapper ul, .kb-wrapper ol { padding-left: 24px; margin: 8px 0; } .kb-wrapper a { color: #032D42; } .kb-wrapper .callout-info { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 10px 14px; margin: 12px 0; border-radius: 0 4px 4px 0; } .kb-wrapper .callout-warning { border-left: 4px solid #e6a817; background: #fff4e0; padding: 10px 14px; margin: 12px 0; border-radius: 0 4px 4px 0; } .kb-wrapper code { font-family: monospace; background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 5px; border-radius: 3px; font-size: 11pt; } .kb-wrapper .link-disclaimer { font-size: 10pt; font-style: italic; color: #444; margin: 2px 0 10px 0; }

Issue MID Server download or upgrade fails with a 404 Not Found HTTP response in regulated market environments, including the Government Community Cloud (GCC), the National Security Cloud (NSC), and hosts restricted to the DoD NIPRNet.

Symptoms Selecting and downloading a MID Server package from the MID Server > Downloads module on an instance hosted in the GCC or NSC regulated markets returns a 404 Not Found HTTP response status. MID Servers installed on hosts restricted to the DoD NIPRNet fail PreUpgradeCheck or AutoUpgrade because the upgrade package cannot be downloaded from https://install.servicenowservices.mil . Entering the assigned MID Server build URL directly in a web browser on the affected host returns a 404 Not Found HTTP response status. Facts Instances hosted in the GCC and NSC regulated markets connect to Install Service endpoints located within their respective regulated environments, separate from the commercial Install Service at https://install.service-now.com . The Install Services in the GCC and NSC are independent from each other and from the commercial Install Service. They pull MID Server packages from the commercial Install Service. MID Servers on hosts restricted to the DoD NIPRNet can only connect to URLs within the .mil United States Department of Defense domain and are typically configured to download assigned MID Server build packages from https://install.servicenowservices.mil . Release All Versions

Cause The Install Service in the GCC and/or NSC regulated market environment has failed to pull the MID Server build files from the commercial Install Service. This makes the packages unavailable for download, resulting in the 404 Not Found response.

Resolution Note: This issue cannot be resolved by the customer. Resolution requires action by ServiceNow internal teams.

Contact ServiceNow Support and provide the following information:

The instance URL and confirmed hosting environment (GCC, NSC, or NIPRNet) The MID Server build version or package URL returning the 404 response The date and approximate time the failure was first observed ServiceNow Support will engage the appropriate internal teams to restore the MID Server packages in the affected regulated market Install Service.