Can't upgrade MID Server

[Paul125]

Hello, we are on Kingston Patch 9. We have an issue with MID server upgrade which unable to upgrade from patch 6 to patch 9. We have 3 mids installed on the same box 2 of them upgraded correctly but one mid has issue upgrading to patch 9. I tried restarting the agent from the agent file also from the services but when I hit the start mid goes up and showing upgrading and after few seconds mid goes down without upgrading.

I've checked the wrapper log and this is what I see. Can someone give an insight into this issue. Thanks!

INFO   | jvm 1    | 2018/11/07 08:35:21.324 | java.lang.Exception: Cannot complete upgrade, one or more files in the upgrade tree are locked and cannot be upgraded

[tim_broberg · Accepted solution]

Some ideas to try:

1. Check to make sure you don't have two mid server processes running out of the same directory such that the one locks up files the other needs to upgrade.
2. Check logs/agent0.log.0 to see the upgrade progress file by file and maybe get an idea what file is causing the trouble.
3. "Kill 'em all and let God sort 'em out." Stop the mid. Delete the directory. Install from scratch.

[Paul125]

Tim sorry for the late response and thanks for your reply. You are right it is the issue with two processes running from the same directory. I have installed 3 MID agents on the box but I've used different folders in the same drive for the installation like below but for some reason I am seeing 4 MID server processes running in the services. Later I disabled the one that I haven't created then stuck MID was upgraded automatically. From the screenshot yellow marked one that I haven't created other 3 was created by me. Have come across anything like this before. If yes, how can I delete the yellow marked MID service? I really appreciate your help.

Locations:

D:\ServiceNow MID Server 1\mid.kingston-10-17-2017__patch7-06-12-2018_06-21-2018_1724.windows.x86-64\agent

D:\ServiceNow MID Server 2\mid.kingston-10-17-2017__patch7-06-12-2018_06-21-2018_1724.windows.x86-64\agent

D:\ServiceNow MID Server 3\mid.kingston-10-17-2017__patch7-06-12-2018_06-21-2018_1724.windows.x86-64\agent

 

[SNUG AM]

From command prompt run below command

sc delete <ServiceName>

ex c:\> sc delete snc_mid

 refer below link for details step :

https://www.howtogeek.com/howto/windows-vista/how-to-delete-a-windows-service-in-vista-or-xp/ 

[SNUG AM]

Please go through these steps and revert back if you still face the same issue. 

https://community.servicenow.com/community?id=community_article&sys_id=19ee3e48db822780107d5583ca961996

[DuaneNMore]

If these are Windows Servers, then the MID you are having problems with is likely the first MID you installed on the Server. All of the MID Service Services on a single MID Server share the "ServiceNow WMI Collector" service. It may be getting stuck on that Service. Run services.msc; find that service and stop it; then attempt the upgrade.