When a MID Server upgrade starts, the temporary "ServiceNow Platform Distribution Upgrade (<mid server name>)" service will delete everything in the "bin", "lib" and "licenses" folders and then copy the new files to these folders (from the temp folder the zip was extracted to). To delete all files in these folders we have a 2 minutes time-out. The main/original MID Server service has to completely shut down before some of those files are no longer locked, and that can take a while.
For some customers with slow host machine for the MID Server, we might time out before the deletes can be finished, and the upgrade stops. The MID Server remains down.
Steps to Reproduce
These steps will force the issue in a test environment:
- After seeing INFO: Added service `snc-platform-dist-upgrade-midserver-prod-full` to upgrade marker file.
- Put lock on some files in lib or bin folders in a way that the file cannot be deleted in the first place
- See after 2 minutes the MID Upgrade failed.
This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.
If you were upgrading to Kingston or London, and the issue was due to file locks while a Windows MID Server was still shutting down, then it should be possible to recover from this, and allow the upgrade to continue.
- Open the Services control panel applet on the host server
- Make sure the MID Server service is stopped. This is the one named "ServiceNow MID Server_<mid server name> ".
- Find the service named "ServiceNow Platform Distribution Upgrade (<mid server name>)".
Note: If it is not there, you can't do this workaround, and a manual upgrade may be required (see KB0713557).
- Start it.
- After a couple of minutes, check the wrapper and agent logs and see if the MID Server has come back up again on the new version.
Related Problem: PRB1314105