Missing MIDLogFileHandler MID Server Properties Cause MID Servers To Go Into an Infinite Loop of Restarting During Start UpDescriptionIssue:MID Servers are experiencing a flapping issue, where they repeatedly come Up for a few seconds and then go back Down for a few seconds before the MID Server comes back up again, continuously repeating this loop if the MIDLogFileHandler MID Server Properties are missing from the ecc_agent_property table on the instance.Symptoms: • MID Server's State goes Up for a few seconds and then back Down for a few seconds in an infinite loop. • The instance is prior to Australia release. • The below MID Server Property [ecc_agent_property] records are missing on the instance com.service_now.mid.logging.MIDLogFileHandler.compressioncom.service_now.mid.logging.MIDLogFileHandler.cleanupOnStartcom.service_now.mid.logging.MIDLogFileHandler.limitcom.service_now.mid.logging.MIDLogFileHandler.count • MID Server Logs will have below Warnings before restarting during the StartupSequencer and will repeat again after restarting.2025-10-14T09:36:58.433-0500 WARN (StartupSequencer) [GlidePropertiesFileHandler:74] com.service_now.mid.logging.MIDLogFileHandler.count property is missing from ecc_agent_property table. Default value 10 will be used2025-10-14T09:36:58.434-0500 WARN (StartupSequencer) [GlidePropertiesFileHandler:74] com.service_now.mid.logging.MIDLogFileHandler.compression property is missing from ecc_agent_property table. Default value none will be used2025-10-14T09:36:58.434-0500 WARN (StartupSequencer) [GlidePropertiesFileHandler:74] com.service_now.mid.logging.MIDLogFileHandler.cleanupOnStart property is missing from ecc_agent_property table. Default value false will be used2025-10-14T09:36:58.434-0500 WARN (StartupSequencer) [GlidePropertiesFileHandler:74] com.service_now.mid.logging.MIDLogFileHandler.limit property is missing from ecc_agent_property table. Default value 10000000 will be usedSteps to Reproduce Related cases where the issue occurred have so far been where instances on Xanadu were upgraded directly to Zurich skipping over Yokohama. However, the issue can be reproduced on either Yokohama or Zurich instances by deleting the four MIDLogFileHandler using any method to bypass the business rule that prevents their deletion.WorkaroundThis problem is currently under review and targeted to be fixed in Australia release. Subscribe to this Known Error article to receive notifications when more information will be available. Running the following background script or fix script will resolve the issue with the MID Servers staying Up on their own on the next restart in the loop they were stuck in. Procedure For instances on Xanadu, Yokohama and Zurich releases:1. In Background Scripts run the following script: var PROPERTIES = { 'com.service_now.mid.logging.MIDLogFileHandler.compression': { sys_id: '594bf202a391421018141b66471e61ee', defaultValue: 'none' }, 'com.service_now.mid.logging.MIDLogFileHandler.cleanupOnStart': { sys_id: '0ddb3e02a391421018141b66471e61d3', defaultValue: 'false' }, 'com.service_now.mid.logging.MIDLogFileHandler.limit': { sys_id: '6dda3ecea351421018141b66471e61b1', defaultValue: '10000000' }, 'com.service_now.mid.logging.MIDLogFileHandler.count': { sys_id: '1041fcc6a311421018141b66471e6101', defaultValue: '10' } }; for (var propertyName in PROPERTIES) { if (!PROPERTIES.hasOwnProperty(propertyName)) continue; var config = PROPERTIES[propertyName]; var gr = new GlideRecord('ecc_agent_property'); gr.addQuery('name', propertyName); gr.addNullQuery('ecc_agent'); gr.addQuery('sys_domain', 'global'); gr.query(); var oobExists = false; var preservedValue = null; if (gr.next()) { if (gr.getUniqueValue() === config.sys_id) { oobExists = true; } else { preservedValue = gr.getValue('value'); gs.warn('Removing non-OOB global ecc_agent_property {0} (sys_id={1})', propertyName, gr.getUniqueValue()); gr.deleteRecord(); } } if (oobExists) continue; var newPropGR = new GlideRecord('ecc_agent_property'); newPropGR.initialize(); newPropGR.setNewGuidValue(config.sys_id); newPropGR.setValue('name', propertyName); newPropGR.setValue('value', preservedValue !== null ? preservedValue : config.defaultValue); newPropGR.insert(); gs.info('Inserted OOB ecc_agent_property {0} with sys_id {1}', propertyName, config.sys_id); } 2. Restart MID Server 3. MID Server should stay up and runningFor Australia and above: 1. On the instance navigate to fix scripts table (sys_script_fix) 2. Run fix script with name: Ensure MID Log Handler Configs 3. Restart the MID Server 4. MID Server should stay up and runningRelated Problem: PRB1969766