MID Server upgrade failed

[Paul125]

Our instance recently upgraded from Jakarta patch 7 to patch 8a. We have 4 MID servers 3 of them have been upgraded to patch 8a but one MID Server haven't been upgraded and version field showing yellow color. I couldn't see upgrade related link to make a manual upgrade. If anyone experienced this issue before please let me know the solution.

Thanks.

[Paul125]

Doug, problem solved after restarting MID from the box. Thanks for looking into this.

[kkswamy]

Hi Ryan,

There is a module "server issues" under mid server, please go there and check the error message. It happened to us as well about a month back while we upgrading from Jakarta to Kingston. So, i upgraded mid server manually by below steps for time being.

1. Type "downloads" in left navigation bar.
2. Click on 'Downloads' Under MID Server.
3. Check the MID server OS  and 32-bit or 64-bit(generally it is 64-bit).
4. Click and download the zip file which is needed.
5. login to MID Server
6. Copy and paste the downloaded zip file in remote desktop drive(example: C drive).
7. Go to "Services" and stop the "servicenow mid server" service.
8. Modify the existed "agent" folder name and Extract the zip file.
9. Open the "config" file in extracted agent folder in wordpad and modify the servicenow URL as dev or test and username,password "save" it.
10. Run the "installer" batch file in "agent" folder.
11. Enter the required servicenow user credentials and suitable name for MID server.
12. Enter the MID Server credentials to start the mid server.
13.  Go to "services" and check the "Servicenow mid server" is started or not.
14. After 1 or 2 minutes, Go to servicenow, type "MID Servers" in left navigation bar.
15. Click and open the "MID Servers" under Discovery.
16. Check the "Status" and "validated" field values for the MID Server.
17. If the Status is "UP" and validated is NO, then open the mid server and validate using the "validate" related link at bottom.
18. After 1 or 2 minutes, MID Server is validated and version will upgrade to the same servicenow version.

I don't know is this best practice or not, but it usually happens when the mid server name is not matched with the service name in the mid server.

[Paul125]

Thanks for the response Swamy. What was error you had received?

[kkswamy]

i didn't remember the exact error message, but i am sure it must happened because it was upgraded manually by my previous colleagues for previous versions. so it failed this time as well, so i upgraded them manually.

[tim_broberg]

I have hit several upgrade issues in recent upgrade cycles where a few % of our mids failed to come back up after an upgrade.

This post is my attempt to streamline detecting those conditions.

I have also recently seen a case where a few mids would fail to start up and have empty bin and lib directories. - PRB1287413

    - Tim.