Aborting MID Server upgrade due to pre-upgrade check failure: Signature verification failed: Manifest not found

Go to solution
Andy H1
Tera Expert

‎07-22-2020 12:46 PM

"Aborting MID Server upgrade due to pre-upgrade check failure: Signature verification failed: Manifest not found"

Has anyone ever seen this in the "MID Server Issues" related list on a MID server record?

 

Edit:

The error message is only appearing on a few of our MID servers.  All of our MID servers are connecting through the same proxy and are connected to our instance ("Up" status), including the ones displaying the error message.

0 Helpfuls
  • 5,752 Views
1 ACCEPTED SOLUTION

Go to solution
tim_broberg
ServiceNow Employee
ServiceNow Employee

‎07-22-2020 01:57 PM

https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/product/mid-server/concept/c_UpgradeAndTestMIDServer.html

View solution in original post

0 Helpfuls
6 REPLIES 6

Go to solution
Andy H1
Tera Expert
In response to tim_broberg

‎07-22-2020 02:22 PM

Thanks Tim, that link was super useful.  In my case, these errors were logged only once on each affected MID server when we applied the last round of patches 17 days ago.  All MID servers had patched successfully and were on the same build when work completed.  I guess these errors resolved on their own and should have been automatically cleared by the pre-upgrade checker.

0 Helpfuls

Go to solution
tim_broberg
ServiceNow Employee
ServiceNow Employee
In response to Andy H1

‎07-22-2020 02:54 PM

Awesome!

Thanks for the update, Andy.
    - Tim.

0 Helpfuls