Orchestration / Mid Server Issues after London Upgrade

[Kai Tingey]

Hi Guys

I recently upgraded our DEV instance to London patch 2, and am working through some tests to remediate any issues post upgrade.

I found that the mid servers did not automatically upgrade due to connectivity issues, i was also unable to trigger a manual upgrade. I suspect our proxy is blocking it. To resolve this, i downloaded the installation files and upgraded them manually using the information in this article:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0635789

the mid servers are now back up and happy.

I also found that this broke LDAP, but that was easily resolved by reselecting the correct mid server afterwards.

However, orchestration activities are now having issues. For example, a workflow that uses the "query AD" activity is now generating this error:

"Unable to resolve host name: (hostname) and default MID Server null is down/invalid"

I have checked and the default mid server is set correctly in the orchestration -> mid server properties area.

I also checked the same activity in our prod environment and it works without issue. I can't see any other settings that are noticeably different between the two (apart from the version of the mid server). 

Can anyone point me in the right direction to get this up and running again?

thanks

[Kai Tingey · Accepted solution]

found it!

Mid Server -> Applications -> Orchestration was null