Loading of 'init_vncc.xml' Fix Script during upgrade causes the Scheduler to be restarted. As a result, the upgrade is triggered multiple times from different worker threads which makes the Upgrade Monitor hung.DescriptionLoading of 'init_vncc.xml' Fix Script during upgrade causes the Scheduler to be restarted. As a result, the upgrade is triggered multiple times from different worker threads which makes the Upgrade Monitor hang.Steps to Reproduce Run an upgrade to Paris release (for example NewYork to Paris).Look for the loading of the 'init_vncc.xml' Fix Script in the logs.Right after the 'init_vncc.xml' loading is complete, notice the stopping of scheduler log message as shown below.Log Messages: 2020-10-19 23:29:33 (392) worker.0 worker.0 txid=f582b5107000 Loading fix: com.snc.cluster/update/init_vncc.xml2020-10-19 23:29:33 (585) worker.0 worker.0 txid=f582b5107000 Finished Loading fix: com.snc.cluster/update/init_vncc.xml [193ms]2020-10-19 23:29:37 (031) glide.scheduler SYSTEM WorkerThreadManager stopping: glide.scheduler2020-10-19 23:29:37 (031) glide.scheduler SYSTEM WorkerThreadManager stopping: glide.scheduler.worker.02020-10-19 23:29:37 (031) glide.scheduler SYSTEM WorkerThreadManager stopping: glide.scheduler.worker.1> Expected Behavior: Loading of the 'init_vncc.xml' Fix Script should not cause the Scheduler to be restarted.WorkaroundThis problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available. As a workaround, before starting the upgrade, make sure [sys_cluster_control.pause_count] and [sys_cluster_state.pause_count] is zero (0). If the pause count is not zero, update it to zero (0). This has to be done before starting the upgrade.Related Problem: PRB1445132