MID Server Stuck in Restart Loop After Upgrading to Zurich ReleaseIssue <!-- /*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 MID Server is stuck in a continuous restart loop after upgrading to the Zurich release. The logs show the MID Server repeatedly detecting missing logging properties in the ecc_agent_property table despite these properties already existing in the local glide.properties file.Symptoms:- MID Server restart loop- Logs indicating missing logging propertiesSteps to Reproduce:1. Log in to the instance2. Check the files - agent.log / glide properties for MID Server 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 release 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: ; } } 1. Break the Restart Loop:- Stop the MID Server service- Edit the glide.properties file (located in the MID Server's root directory) to add: mid.no_auto_restart=true- Start the MID Server2. Add Missing Properties in ServiceNow:- Log into the ServiceNow instance- Navigate to MID Server > Properties- Verify these properties exist (with empty ecc_agent field):com.service_now.mid.logging.MIDLogFileHandler.countcom.service_now.mid.logging.MIDLogFileHandler.compressioncom.service_now.mid.logging.MIDLogFileHandler.cleanupOnStartcom.service_now.mid.logging.MIDLogFileHandler.limit- If missing, create them with these values: (NOTE: These may be different depending on your instance, so take the values from your instance)com.service_now.mid.logging.MIDLogFileHandler.count=10com.service_now.mid.logging.MIDLogFileHandler.compression=nonecom.service_now.mid.logging.MIDLogFileHandler.cleanupOnStart=falsecom.service_now.mid.logging.MIDLogFileHandler.limit=100000003. Restore Normal Operation:- Stop the MID Server- Remove the mid.no_auto_restart=true line from glide.properties- Start the MID ServerImportant Notes:- Do not manually edit the logging properties in glide.properties after this fix- All future changes to these properties should be made through the ServiceNow interface- This issue is documented in KB1637658 and is related to logging handler changes introduced in Xanadu and carried forward to Zurich