MID Servers stuck upgrading from New York Patch1-Hotfix1a to Patch4-Hotfix1

[amoss98]

Hi all,

I was hoping someone might have a better idea where to look as I'm relatively new to ServiceNow and not really sure what else to check:

Our instance was recently updated to New York Patch 4-Hotfix 1 and thus our MID Servers also attempted to upgrade from New York Patch 1 - Hotfix 1a to the same version. Unfortunately, they continue to show in a "Down" status. I have attempted to place them back in an Up status, restart them , and manually start the upgrade again from our instance but it looks like they all are getting stuck on "Deploy Binary Packages" if I go in to the MID Server Upgrade History and view the complete upgrade details. We've also restarted the VMs that are running the MID Servers but they are getting stuck at the same spot when the try to start the upgrade again.

[SatheeshKumar]

Try the below!!  If this doesnt helps, check the link at the end

Upgraded MID Servers running multiple services

Beginning with the New York release, a batch file in the MID Server installer package ensures that only one Windows MID Server service is configured for an executable path (MID Server installation folder). Previous versions have not checked for this configuration. MID Servers upgraded to New York or later that run multiple services with the same executable path are prevented from starting. If you experience this issue, follow this procedure to reconfigure the MID Server to use only one service:

1. Delete the unwanted Windows service by running sc.exe delete <service name> from the command line.
2. Open the wrapper-override.conf file in the MID Server installation folder.
3. Change the wrapper.name and wrapper.displayname parameters to the service name that you want to keep.
4. Restart the MID Server.

Check the below links

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

[amoss98 · Accepted solution]

Thanks for the reply!

I ended up referencing a couple other articles from the link provided that were able to point me in the correct direction. Upon checking the upgrade logs in the C:\Windows\Temp\*number*\upgrade-wrapper\logs folder I was able to find this error was holding things up:

C:\Program Files\ServiceNow\agent\bin\sw_wmi\bin\wmi_collector.exe cannot be deleted

Turns out the ServiceNow WMI Collector service hadn't stopped and was locking a file as the above error describes. Stopping that service allowed the update to finish.

Continuing an upgrade after the MID Server is down:

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

MID Server Upgrade Process:

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

Restarting the WMI Collector service after errors:

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