Midserver down after zurich upgrade to patch3

[njsamuel]

We recently upgraded our instance from Xanadu Patch 10 to Zurich Patch 3, following which our MID Server (ID: c872d00bdb225380299fe1d3ca9619d6) has been consistently failing. Upon attempting to restart, the server comes online briefly (for about a minute) before going down again.

We’ve conducted thorough checks including:

• Verifying and refreshing credentials
• Coordinating with our infrastructure team to validate local host configurations
• Reviewing all known configurations and logs

Despite these efforts, the issue persists. The error message we’re receiving is:

"User midsrvdev associated with down MID Server: c872d00bdb225380299fe1d3ca9619d6. No login attempts within reporting period."

This is affecting our non-production instance, which is business-critical as we are scheduled to upgrade our production environment within the next week. Timely resolution is essential to ensure readiness and avoid disruption to our upgrade timeline.

[njsamuel]

Issue:
After upgrading the instance to Zurich Patch 3, the MID Server repeatedly starts and stops.
From the logs, we observed the following messages indicating that the properties related to the MID log handler were missing in the instance table ecc_agent_property:

com.service_now.mid.logging.MIDLogFileHandler.count property is missing from ecc_agent_property table
com.service_now.mid.logging.MIDLogFileHandler.compression property is missing from ecc_agent_property table
com.service_now.mid.logging.MIDLogFileHandler.cleanupOnStart property is missing from ecc_agent_property table
com.service_now.mid.logging.MIDLogFileHandler.limit property is missing from ecc_agent_property table
Restarting MID Server as MID glide.properties file has been updated with settings from the Instance

As a result, the MID continuously updates its local glide.properties file and restarts, never reaching the "Up" state.

Solution Proposed:
Please add the following four properties manually under MID Server > Properties (table: ecc_agent_property) or import the attached XML file (ecc_agent_property.xml) directly into your instance:

Property Name Value

com.service_now.mid.logging.MIDLogFileHandler.count	10
com.service_now.mid.logging.MIDLogFileHandler.compression	none
com.service_now.mid.logging.MIDLogFileHandler.cleanupOnStart	false
com.service_now.mid.logging.MIDLogFileHandler.limit	10000000

After importing or creating them manually, restart the MID Server service once on the host.
The MID should now stabilize and remain in the Up state.

[njsamuel]

SN gave us the xml file that we needed to uploaed and on the call , we did the needful and resolved the issue.