While running the MID Server auto upgrade sometimes it may fail and during investigation we may find the below error message in agent/wrapper logs.
07/02/18 18:54:01 (389) Worker-Interactive:HeartbeatProbe Worker completed: HeartbeatProbe time: 0:00:00.000 07/02/18 18:54:29 (733) LogStatusMonitor.60 stats threads: 42, memory max: 910.0mb, allocated: 122.0mb, used: 29.0mb, standard.queued: 0 probes, standard.processing: 0 probes expedited.queued: 0 probes, expedited.processing: 0 probes interactive.queued: 0 probes, interactive.processing: 0 probes 07/02/18 18:55:29 (733) LogStatusMonitor.60 stats threads: 42, memory max: 910.0mb, allocated: 123.0mb, used: 29.0mb, standard.queued: 0 probes, standard.processing: 0 probes expedited.queued: 0 probes, expedited.processing: 0 probes interactive.queued: 0 probes, interactive.processing: 0 probes 07/02/18 18:56:06 (342) AutoUpgrade.3600 Result of PowerShell test: true WARN: MID Server Windows Service is not running as LocalSystem and administrative rights cannot be determined
Every hour from instance we trigger a probe to check if the MID Server is up-to-date or not. If we find that the MID Server version is not matching with the instance MID version then we will trigger the upgrade probe. When this is triggered, on the MID server the service will try to get the latest package form the "install.service-now.com". This package is stored in the temporary folder (temp). Once the download is finished then it will replace the existing agent folder with newly downloaded package.
As part of the upgrade, the MID Server will install a new service "ServiceNow Platform Distribution Upgrade" which will handle the deletion of the old MID Server files and installation of the new files.
Microsoft requires administrator access on the local machine in order to install a new service. As such we make it a requirement for the MID Server service user to be the Local System or local administrator.
There are two supported configurations for a MID Server service:
- Run as Local System (default) OR
- Run as a user with local administrator rights to the MID Server host
You can set-up explicit security roles and file permissions to get upgrades to work, but it will not be supported.