Loading...
Loading...
An issue has been identified where a MID Server is experiencing a flapping issue, where it will 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. This issue has been experienced when 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 Xanadu, Yokohama or Zurich. • The below MID Server Property [ecc_agent_property] records are missing on the instance: com.service_now.mid.logging.MIDLogFileHandler.compression com.service_now.mid.logging.MIDLogFileHandler.cleanupOnStart com.service_now.mid.logging.MIDLogFileHandler.limit com.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 used 2025-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 used 2025-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 used 2025-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 used
Steps to reproduce are under review.
The problem is currently under review and targeted to be fixed in Australia, Zurich Patch 8, and Yokohama Patch 13. Subscribe to this Known Error article to receive notifications when more information will be available. The workaround fix script (below) can be run to add the missing Midserver properties and address this issue. The fix script will create the missing properties with the correct sys_id values (listed in the table below). Please do not manually add the properties by name as this will not create the properties with the correct sys_id values expected by the platform. If the properties were previously or inadvertently manually created and have a different sys_id than listed in the table below, run the fix script provided below and it will recreate the properties with the correct sys_id values. ServiceNow will perform maintenance to apply this fix script on impacted customer instances. Impacted customers will be notified via Customer Communication record.
For instances on Xanadu, Yokohama and Zurich releases: 1. Navigate to System Maintenance, select Scripts - Background and 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 running For instances on Australia releases 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 running FAQs : Q: When will this planned maintenance happen? A: A COMM record will be sent to notify you with the dates and times if an instance is determined for maintenance. Q: What does the planned maintenance do? A: It will add these MID Server Property [ecc_agent_property] records if they are missing on the instance: MID Server Property sys_id (property must have this specific sys_id value populated by the fix script) default value com.service_now.mid.logging.MIDLogFileHandler.cleanupOnStart 0ddb3e02a391421018141b66471e61d3 false com.service_now.mid.logging.MIDLogFileHandler.compression 594bf202a391421018141b66471e61ee none com.service_now.mid.logging.MIDLogFileHandler.count 1041fcc6a311421018141b66471e6101 10 com.service_now.mid.logging.MIDLogFileHandler.limit 6dda3ecea351421018141b66471e61b1 10000000 Q: Is there a query I can apply to my instance to check for these properties? A: Yes, append this query to your instance url to search for the four required MID server properties by their expected sys_id values: /ecc_agent_property_list.do?sysparm_query=sys_id%3D0ddb3e02a391421018141b66471e61d3%5EORsys_id%3D594bf202a391421018141b66471e61ee%5EORsys_id%3D1041fcc6a311421018141b66471e6101%5EORsys_id%3D6dda3ecea351421018141b66471e61b1&sysparm_view= Q: Can I opt-out of this maintenance? A: Yes, you may opt out of the maintenance; however we recommend applying the workaround fix script on your own as soon as possible. Q: Will there be any implications if the workaround script is run before the maintenance and we do not opt out of the maintenance? A: No, there won't be any implications as it will skip since the properties already have the expected value. Q: Is there any issue with running the fix script more than once on the same instance? A: No, there won't be any issue as the fix script will skip any update if the properties already have the expected value. Q: What if my instance has the MID server properties when I query on the name, but the sys_id is different than what is shown in the table above? A: Each property must have the sys_id values as shown in the table above. Please apply the fix script as soon as possible which will recreate each property with the correct sys_id value expected by the platform.
PRB1969766
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.