MID Server Service Startup Error "redirect count exceeded or request did not finish within 60 seconds" - Support and Troubleshooting

MID Server Service Startup Error "redirect count exceeded or request did not finish within 60 seconds" Issue The MID Server is down and the following error is seen on the agent logs when the MID Server Service is started:

StartupSequencer ECC Sender Cache initialization: step 1 of 4: setting up cache directories... StartupSequencer ECC Sender Cache initialization: step 2 of 4: building list of sysids from each file in cache directories... StartupSequencer ECC Sender Cache initialization: step 3 of 4: for all ECC Queue output records assigned to this MID Server which are in Processing state: change state to Ready... StartupSequencer Setting all ECC queue output records from processing state to ready for agent: mid.server.MID_NAME StartupSequencer SEVERE *** ERROR *** SOAP Request: mid.server.MID_NAME UpdateQueueFromProcessingToReady StartupSequencer SEVERE *** ERROR *** SOAP Response: Status code=500, Response body= SOAP-ENV:Server Transaction cancelled: SOAPProcessorThreade4991acc1b58f81491e4caee034bcb51: redirect count exceeded or request did not finish within 60 seconds - terminating request... Error completing SOAP request StartupSequencer SEVERE *** ERROR *** UpdateQueueFromProcessingToReady: unable to connect after 5 retries due to null StartupSequencer SEVERE *** ERROR *** java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at com.glide.util.ClassUtil.newInstance(ClassUtil.java:189) at com.service_now.mid.services.Monitors.createMonitorWithoutStarting(Monitors.java:280) at com.service_now.mid.services.Monitors.createMonitor(Monitors.java:270) at com.service_now.mid.services.Monitors.loadInternalMonitor(Monitors.java:204) at com.service_now.mid.services.Monitors.loadInternalMonitors(Monitors.java:129) at com.service_now.mid.services.Monitors.start(Monitors.java:63) at com.service_now.mid.services.Monitors.onMIDServerEvent(Monitors.java:408) at com.service_now.mid.services.Events.internalFire(Events.java:102) at com.service_now.mid.services.Events.fire(Events.java:34) at com.service_now.mid.services.StartupSequencer.startServices(StartupSequencer.java:380) at com.service_now.mid.services.StartupSequencer.testsSucceeded(StartupSequencer.java:162) at com.service_now.mid.services.StartupSequencer.startupSequencerRunnable(StartupSequencer.java:707) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.io.IOException: setQueueProcessingToReady failed at com.service_now.monitor.ECCSenderCache. (ECCSenderCache.java:154) at com.service_now.monitor.ECCSender. (ECCSender.java:85) Cause When the MID server is started it will set any output ecc_queue records for the MID from processing to ready. Some MID servers may have a very large number of outputs in processing. Because of this, the call to set the records to "ready" takes longer than a minute and the transaction is canceled.

Resolution First, confirm there is a large number of outputs for this MID Server in the "processing" state To confirm, navigate to the ecc_queue table and use the following filter: Agent = mid.server.affected_mid_server_name State = processing Queue = output Once confirmed, set such records to state = ready Setting the records to ready state: This could be done via a script background Alternatively, this could be done via the UI Set records to ready state via the UI: Stop the affected MID Server service Navigate to the ecc_queue table and use following filter: Agent = mid.server.affected_mid_server_name State = processing Queue = output On the list, right-click on one of the column headers and select "Update All" Click ok on the "Ok" option in the pop up for "Update the entire list? ( records)" (there will be a record count that should match what you see in the current list) Set state to "ready" Click "Update" Note: The transaction could timeout due to a large number of records to be updated. The step may need to be repeated a couple of times. Review the count of processing records as seen in step 2 and confirm the list is either empty or has fewer records than before Startup the MID Server service