MID Server Fails to connect to the instance after upgrading to TokyoIssue After upgrading to Tokyo, MID Server fails to connect to the instance.Below errors can be seen in the Agent and Wrapper logs. Agent Log Error: 2022-11-24T20:43:48.965+0800 ERROR (StartupSequencer) [MIDServer:119] Synchronous HTTP request to the instance to query for assigned-packages failed. com.service_now.mid.dist.upgrade.UpgradeException: Unable to refresh packages. No document result returned from MIDAssignedPackages query at com.service_now.mid.services.Packages.refresh(Packages.java:129) at com.service_now.mid.services.Packages.refresh(Packages.java:134) at com.service_now.mid.MIDServer.canUpgrade(MIDServer.java:117) at com.service_now.mid.services.StartupSequencer.startServices(StartupSequencer.java:397) at com.service_now.mid.services.StartupSequencer.testsSucceeded(StartupSequencer.java:179) at com.service_now.mid.services.StartupSequencer.startupSequencerRunnable(StartupSequencer.java:734) at java.base/java.lang.Thread.run(Thread.java:829)Caused by: java.lang.IllegalStateException: No document result returned from MIDAssignedPackages query at com.service_now.mid.MIDAssignedPackagesQuery.query(MIDAssignedPackagesQuery.java:90) at com.service_now.mid.services.Packages.determineAssignedPackages(Packages.java:234) at com.service_now.mid.services.Packages.refresh(Packages.java:122) ... 6 more========================================================== Wrapper Log Error: 2022/11/24 22:25:43 | at com.google.inject.internal.InternalProvisionException.toProvisionException(InternalProvisionException.java:251)2022/11/24 22:25:43 | at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1103)2022/11/24 22:25:43 | at com.service_now.mid.services.Monitors.lambda$start$0(Monitors.java:74) 2022/11/24 22:25:43 | Caused by: java.lang.RuntimeException: Failure creating instance of ECCSenderCache, unable to continue2022/11/24 22:25:43 | at com.snc.midserver.monitor.eccsender.internal.ECCSenderModule.provideEccSenderCache(ECCSenderModule.java:111)2022/11/24 22:25:43 | at com.snc.midserver.monitor.eccsender.internal.ECCSenderModule$$FastClassByGuice$$4726282.GUICE$TRAMPOLINE(<generated>) 2022/11/24 22:25:43 | Caused by: java.io.IOException: Could not get aggregate count of 'processing' state ecc_queue records for this MID.2022/11/24 22:25:43 | at com.service_now.mid.MIDServerInfoRemote.getEccQueueProcessingSysIds(MIDServerInfoRemote.java:246)2022/11/24 22:25:43 | at com.service_now.mid.Instance.getQueueProcessingSysIds(Instance.java:187)=========================================================CauseIn Tokyo, changes were made to the ECCSenderCache startup code that required changes to one of the web services on the instance (GetMIDInfo). The above errors are seen after the upgrade if only the MID Server code is updated but not the instance's web service code due to any upgrade issues.ResolutionPlease verify that the below Scripted Web Services that belong to the MID Server package are updated to the expected version (Tokyo): https://<instance_name>.service-now.com/sys_web_service_list.do?sysparm_query=sys_package.name=MID%20Server If any of the above web services are failed to upgrade, please repair the MID Server plugin (com.glideapp.agent) to restore the correct files needed to upgrade the MID Server package from Rome to Tokyo.