- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2021 10:38 AM
Hi everyone and thank you for taking your time to review this issue. One of our MID servers upgraded successfully through Auto-Upgrade and the second MID server in the cluster threw the following error - WARNING *** WARNING *** Unable to determine upgrade scenario with current=paris-06-24-2020__patch5-hotfix2-01-20-2021_01-21-2021_0752 assigned=quebec-12-09-2020__patch2-03-17-2021_03-25-2021_1921.
I am unable to locate anything specific to this and wanted to know if there is anyone who may have experienced a similar situation. We would like to understand how to overcome the problem and get the server back to an auto-upgrade status on the latest release.
Thanks for your time and help.
Solved! Go to Solution.
- Labels:
-
Instance Configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2021 11:28 AM
Hi Sachin. The information cam directly from the MID server logs. That was all the log recorded. I do want to let you know that I clicked on the "Upgrade Server" link and the server immediately came up and showed validated. This is very unusual I believe so I don't want to waste anyone's time chasing ghosts.
Thank you so much for your suggestion and I will check that that property is active.
Regards,
Jeff

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2021 10:42 AM
did you check mid server logs?
It will tell you exact issue.
Set the property mid.log.level=trace to see detailed verification debug messages.
Regards,
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2021 11:28 AM
Hi Sachin. The information cam directly from the MID server logs. That was all the log recorded. I do want to let you know that I clicked on the "Upgrade Server" link and the server immediately came up and showed validated. This is very unusual I believe so I don't want to waste anyone's time chasing ghosts.
Thank you so much for your suggestion and I will check that that property is active.
Regards,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2021 07:53 AM
glad this resolved itself. I just ran into the issue myself. still working through it though. In the gui I don't have the option to upgrade. I also dug through the agent.log file and found references to com.snc.dist.mid_upgrade.UpgradeException: java.io.FileNotFoundException: D:\ServiceNow\agent\bin\mid.bat (Access is Denied) which says to enable the windows agent experience service which I did. Now I want it to try and upgrade again and not have to manually reinstall everything. It's also really odd since we have 2 other mid service instances running on the same server and they upgraded ok.
06/27/21 07:40:39 (809) AutoUpgrade.3600 WARNING *** WARNING *** Unable to determine upgrade scenario with current=paris-06-24-2020__patch4b-02-04-2021_02-08-2021_1058 assigned=quebec-12-09-2020__patch2-03-17-2021_03-25-2021_1921