MID Server fails to start - Failure creating instance of ECCSenderCache - GetQueueSysIdsByState method missing in GetMIDInfoIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } MID Server starts, but immediately shuts itself down. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } In the MID Server agent0.log.0 file: 2025-10-16T14:58:19.851-0400 INFO (StartupSequencer) [MonitorRunner:97] Enabling monitor: ECCQueueMonitor 2025-10-16T14:58:19.867-0400 INFO (StartupSequencer) [ECCSenderCache:215] ECC Sender Cache initialization: step 1 of 5: setting up cache directories... 2025-10-16T14:58:19.869-0400 INFO (StartupSequencer) [ECCSenderCache:222] ECC Sender Cache initialization: step 2 of 5: building list of sysids from each file in cache directories... 2025-10-16T14:58:19.871-0400 INFO (StartupSequencer) [QueueProcessingTracker:97] Initializing state cache with 0 sys_ids from ECCSender work output directory files. 2025-10-16T14:58:20.224-0400 INFO (StartupSequencer) [MIDServerInfoRemote:281] Getting 0 ECC queue output record sys_ids for agent: mid.server.copa_hrsd_tst_grnfld 2025-10-16T14:58:20.334-0400 INFO (StartupSequencer) [MIDServerInfoRemote:281] Getting 79 ECC queue output record sys_ids for agent: mid.server.copa_hrsd_tst_grnfld 2025-10-16T14:58:20.443-0400 ERROR (StartupSequencer) [StartupSequencer:178] StartupSequencer threw exception, unable to perform proper startup, shutting down com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) [Guice/ErrorInCustomProvider]: RuntimeException: Failure creating instance of ECCSenderCache, unable to continue at ECCSenderModule.provideEccSenderCache(ECCSenderModule.java:112) \_ installed by: InternalMonitorModule -> ECCSenderModule at ECCSenderModule.provideEccSender(ECCSenderModule.java:86) \_ for 2nd parameter at ECCSenderModule.provideEccSender(ECCSenderModule.java:86) \_ installed by: InternalMonitorModule -> ECCSenderModule while locating ECCSender at ECCSenderModule.configure(ECCSenderModule.java:70) \_ installed by: InternalMonitorModule -> ECCSenderModule while locating AMonitor annotated with @Element(setName=,uniqueId=191, type=MAPBINDER, keyType=String) Learn more: https://github.com/google/guice/wiki/ERROR_IN_CUSTOM_PROVIDER 1 error ====================== Full classname legend: ====================== AMonitor: "com.snc.midserver.monitor.spi.AMonitor" ECCSender: "com.service_now.monitor.ECCSender" ECCSenderModule: "com.snc.midserver.monitor.eccsender.internal.ECCSenderModule" Element: "com.google.inject.internal.Element" InternalMonitorModule: "com.snc.midserver.monitor.internal.InternalMonitorModule" ======================== End of classname legend: ======================== at com.google.inject.internal.InternalProvisionException.toProvisionException(InternalProvisionException.java:251) ...Caused by: java.lang.RuntimeException: Failure creating instance of ECCSenderCache, unable to continue ... Caused by: java.io.IOException: Failure retrieving sys IDs of ECC queue records in processing state ... Caused by: com.snc.midserver.midinfo.api.MIDServerInfoException: No 'sysIds' array returned in response. A possible reason for this issue could be that the sys_web_service.GetMIDInfo service is either outdated or experiencing a problem. at com.snc.midserver.midinfo.internal.MIDServerInfoRemote.getQueueSysIdsByState(MIDServerInfoRemote.java:308) at com.service_now.mid.Instance.getQueueSysIdsByState(Instance.java:196) ... 53 more 2025-10-16T14:58:22.657-0400 INFO (Wrapper-Stopper) [Main:389] Stopping MID server In the instance appnode localhost logs: SOAPProcessorThread28021c089799f610eb71b4d6f053af15 2ED154449799F610EB71B4D6F053AF12 txid=e802d8089799 *** Script: Unsupported request type: GetQueueSysIdsByState Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Zurich and later only for this specific cause. Other causes exist - see KB1276386. Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The suggestion in the logs "the sys_web_service.GetMIDInfo service is either outdated or experiencing a problem." is likely when the instance side appnode logs confirm "Unsupported request type: GetQueueSysIdsByState". That means the GetMIDInfo Scripted SOAP Service script is an old version and doesn't include the code to handle the GetQueueSysIdsByState function at all. That method was added by PRB1709965 in the Zurich version ('MID Server Failover: Certain failover scenarios can result in duplicate ecc_queue input messages for MID Server Clusters' Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } You will need to revert/upgrade the 'GetMIDInfo" scripted SOAP service to the correct version. Go to the list of Scripted SOAP Services, filter on Package=MID ServerOpen 'GetMIDInfo' and check the Files properties to see if it is a custom version.https://<instance>.service-now.com/sys_web_service.do?sys_id=9d5754c5ff7200006857361332f49d5chttps://<instance>.service-now.com/sys_metadata.do?sys_id=9d5754c5ff7200006857361332f49d5c&sysparm_ignore_class=trueIf it is custom, revert it to the current System version.If not, check the Upgrade history, and Customer updates table, as custom records present there would also be a sign that it is custom, and needs reverting.https://<instance>.service-now.com/sys_update_xml_list.do?sysparm_query=GOTOname%3Dsys_web_service_9d5754c5ff7200006857361332f49d5c&sysparm_view=https://<instance>.service-now.com/sys_update_version_list.do?sysparm_query=GOTOname%3Dsys_web_service_9d5754c5ff7200006857361332f49d5c&sysparm_view= If there is no sign of any customisation, then check the upgrade history:https://<instance>.service-now.com/sys_upgrade_history_log_list.do?sysparm_query=GOTOfile_name%3Dsys_web_service_9d5754c5ff7200006857361332f49d5c&sysparm_view=If the status is Skipped, then revert it .If the status is unchanged, then the upgrade engine has got confused, and you probably have bad record in sys_upgrade_state: https://<instance>.service-now.com/sys_upgrade_state_list.do?sysparm_query=GOTOname%3Dsys_web_service_9d5754c5ff7200006857361332f49d5c.xml&sysparm_view=If there is a record there, then delete it. Then repair the MID Server plugin. This is a screenshot of what the Updated timestamps should look like for a Zurich Patch 3 instance (give or take the timezone/hour). Even if you are on a newer version than that, if you have any older ones, then the records are probably old skipped upgrades: Other potential causes of ECCSenderCache errors where "Unsupported request type: GetQueueSysIdsByState" isn't the cause are listed in:KB1276386 Failure creating instance of ECCSenderCache, unable to continue