Mid Server Issues

[Niks3562]

Hi,

When I am trying to restart the GCP mid server then it will throw 2 errors in ServiceNow.

1. MID Server failed to upgrade

2. Reinstall Service verification was failed during MID Server upgrade. It is possible that a required service re-installation was skipped. Make sure that the Service is installed with the same version as MID Server after upgrade.

Thanks in Advance

Nikita

[Sandeep132]

Hi @Niks3562 , As mentioned in the 2nd message MidServer upgrade got skipped during your upgrade. Try to upgrade the midserver manually and it should fix the issue.

[Niks3562]

Hi Sandeep,

How can we manually upgrade the mid server?

Regards

[Dr Atul G- LNG]

Hi @Niks3562 

1. Navigate to MID Server - Downloads.
2. Select the link for your MID Server host's platform to download. ...
3. Copy the ZIP file to the MID Server host.
4. Extract the ZIP file to a temporary folder.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0713557

This kB is helpful. 

[Dr Atul G- LNG]

Hi @Niks3562 

Resolution

Pre-Upgrade Steps: 

1. Save logs and other details of the failed upgrade, so that it may be possible to find the cause later on.
2. Gather the required information and configuration settings:
   
   • Instance Username and Password, for the instance user that the MID Server logs in as. 
   • Proxy server information if used, including the proxy server, username and password.
   • Host server running the MID Server, the install folder and the Service name for it. 
   • Have remote desktop access as an administrator to the host server
3. Backup the following files:
   
   • agent\config.xml
   • agent\conf\wrapper-override.conf
   • agent\jre\lib\security\cacerts
   • agent\keystore\agent_keystore.jks (In Rome, the location of the "agent_keystore.jks" file is in "...agent\security" folder).
4. Download the current full MID Server package from your ServiceNow instance
   
   • Navigate to MID Server - Downloads
   • Select the link for your MID Server host's platform to download. If unsure, use the 64 bit link.
   • Copy the ZIP file to the MID Server host.
   • Extract the ZIP file to a temporary folder. Ensure there are no errors extracting the ZIP file.
   • If you are blocked from downloading from install.service-now.com, then enable system property: mid.download.through.instance=true

Upgrade Steps: 

1. Make sure there are no scheduled jobs happening using the MID Server during the procedure especially if performing it in a PRODUCTION instance. Checking that no ECC Queue output records for the MID Server are currently in Ready or Processing state is also advised.
2. Stop the Mid Server service. 
3. Go to the existing MID Server installation folder, and rename the existing 'agent' folder and move it to a different location.
   
   • Use a name such as 'agent_old-do_not_run' or similar so there is no confusion in future.
   • If this is not possible because of files still in use by the operating system, then set the Service startup to Manual, and restart the server to free up the files.
4. Move the recently extracted 'agent' folder to the original agent folder's location.
5. Manually update the following files based on the information from the backup files, and credential information gathered earlier
   
   • config.xml
     
     • url, mid.instance.username, mid.instance.password, name
     • mid_sys_id and keypairs.mid_id
     • Other likely custom values:
       
       • mid.proxy.use_proxy, and the various mid.proxy.* parameters, if a Proxy is used between the MID Server and Instance
       • threads.max, threads.expedited.max, threads.interactive.max if different from the defaults
       • instance.date.format if different from the default
   • conf/wrapper-override.conf
     
     • wrapper.name, wrapper.displayname.
       Note: These need to match the existing Windows Service name and display name. If the upgrade failed due to a mismatch, then that can be corrected now to match the windows service.
6. For version before Rome, create a "keystore" folder under the "agent" folder, and copy the "agent_keystore.jks" file into it. For Rome, just delete the "agent_keystore.jks" file from the ".../agent/security" folder.
   
   1. NOTE - We have seen in some cases that if this file is also copied over a MID server issue appears saying "Could not decrypt file discovery inclusion list after sync" after the restore. 
   2. In such as case, after the rest of this restore process is completed do the following:
      
      • 1) Stop the mid server service on the host machine, deleted the agent\keystore folder and start the MID server service.
      • In Rome, the location of the "agent_keystore.jks" file is in "...agent\security" folder)
      • 2) The Keystore folder will be created automatically when the service is started.
      • 3) Now login to the ServiceNow instance and validate the mid server.
      • 4) Wait for 2-5 minutes the error "Could not decrypt file discovery inclusion list after sync" should be gone from "MID SERVER ISSUE TAB".
   3. If you so choose, you can not copy this file and then you will have to validate the MID after the rest of the manual restore is completed.
7. If you had a custom cacerts file, with SSL Certificates added to it, then copy the backup "cacerts" file over the empty one in the "agent\jre\lib\security" folder
8. Start the existing MID Server service. 
9. Check the MID Server from the instance if the Status is UP.
10. Validate the MID Server if necessary.