- 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 04:25 AM
Yeah, looks to me like it's got nothing to do with instance at all. I'll update this thread after HI Support gives an answer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2022 04:31 AM
By instance I meant it is happening on your instance and mid server is something we can't even replicate so it becomes hard to debug through discussion.
- 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.