- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2022 02:38 AM - edited 11-18-2022 06:10 AM
Please point me in the right direction, a client recently upgraded from Rome to Tokyo and the MID Server has failed.
MID-Server Record says the following:
Reported MID Server version 'rome-06-23-2021__patch10-hotfix2a-09-02-2022_09-28-2022_1908' is not compatible with instance version 'tokyo-07-08-2022__patch1-09-01-2022_09-16-2022_1610'. Upgrade is required. More Info
Link is dead btw.
Then, on the Server Issues record there is an Update Check record which says:
Aborting MID Server upgrade due to pre-upgrade check failure: Unable to download updates from install server
Ok, maybe I can download the new version and install it then. By going to the Downloads section. Click the link:'https://install.service-now.com/glide/distribution/builds/package/app-signed/mid-windows-installer/2...
403 forbidden error:
Forbidden
You don't have permission to access /glide/distribution/builds/package/app-signed/mid-windows-installer/2022/09/16/mid-windows-installer.tokyo-07-08-2022__patch1-09-01-2022_09-16-2022_1610.windows.x86-64.msi on this server.
Update:
My initial thoughts were correct, it had nothing to do with instance and everything to do with the install.servicenow.com server
Solved! Go to Solution.
- Labels:
-
MID Server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2022 06:11 AM
HI Support fixed the issue, as I initially thought, it had nothing to do with the instance and the issue was on install.servicenow.com server location not being accessable from my location.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2022 03:07 AM
Hello,
Whenever the upgrade happens issues with mid server are pretty common.
Please check the below support article which has all the trouble shooting steps for the same:-
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0596459
Please mark my answer as correct based on Impact.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2022 03:38 AM
Yeah, it seems the same error is in the error logs as well, 403 error:
2022-11-15 12:13:20 (835) AutoUpgrade.3600 Downloaded: []
2022-11-15 12:13:21 (007) AutoUpgrade.3600 Setting mid status to Upgrading
2022-11-15 12:13:21 (007) AutoUpgrade.3600 Instance.updateAgentRecordState(), OperationalState=UPGRADING
2022-11-15 12:13:21 (335) AutoUpgrade.3600 Performing pre-upgrade validation tests.
2022-11-15 12:13:21 (335) AutoUpgrade.3600 Downloading from https://install.service-now.com/glide/distribution/builds/package/app-signed/mid-upgrade/2022/09/16/...
2022-11-15 12:13:22 (241) AutoUpgrade.3600 WARNING *** WARNING *** Method failed: (https://install.service-now.com/glide/distribution/builds/package/app-signed/mid-upgrade/2022/09/16/...) HTTP/1.1 403 Forbidden with code: 403
2022-11-15 12:13:22 (241) AutoUpgrade.3600 SEVERE *** ERROR *** Method failed: (https://install.service-now.com/glide/distribution/builds/package/app-signed/mid-upgrade/2022/09/16/...) HTTP/1.1 403 Forbidden with code: 403
2022-11-15 12:13:22 (241) AutoUpgrade.3600 SEVERE *** ERROR *** Method failed: (https://install.service-now.com/glide/distribution/builds/package/app-signed/mid-upgrade/2022/09/16/...) HTTP/1.1 403 Forbidden with code: 403
2022-11-15 12:13:22 (241) AutoUpgrade.3600 SEVERE *** ERROR *** Aborting MID Server upgrade due to pre-upgrade check failure: Unable to download updates from install server
2022-11-15 12:13:22 (600) AutoUpgrade.3600 Setting mid status to Upgrade Failed
2022-11-15 12:13:22 (600) AutoUpgrade.3600 Instance.updateAgentRecordState(), OperationalState=UPGRADE_FAILED
2022-11-15 12:13:22 (694) AutoUpgrade.3600 SEVERE *** ERROR *** MID Server upgrade failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2022 03:45 AM
hello,
Were you able to solve the issue using the above article?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2022 03:49 AM
No, I get a 403 error. As far as I can tell I get that same error no matter which version I try the link from.