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

[Andy H1]

"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.

[Ashutosh Munot1]

https://hi.service-now.com/kb_view.do?sysparm_article=KB0565184 Check this out. Thanks, Ashutosh

[Andy H1]

Thanks Ashutosh,

The error I'm getting is different than the one in the link you provided.  I'm not able to verify connectivity using the steps in the "Test MID Server Connectivity" link in that HI article.  All our MID servers are connecting through a proxy that blocks all the options that are listed.

There's definitely outbound connectivity however.  All our MID servers are in "Up" status and responding to restart commands.

[Andy H1]

Thanks Ashutosh,

The error I'm getting is different than the one in the link you provided.  I'm not able to verify connectivity using the steps in the "Test MID Server Connectivity" link in that HI article.  All our MID servers are connecting through a proxy that blocks all the options that are listed.

There's definitely outbound connectivity however.  All our MID servers are in "Up" status and responding to restart commands.

[tim_broberg · Accepted solution]

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