Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Midserver down after zurich upgrade to patch3

njsamuel
Tera Contributor

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.

6 REPLIES 6

Steven Coda
Tera Expert

Hello,  There are two KB Articles from ServiceNow outlining this issue,  please see these documents so that you are able to take required steps to resolve.  I hope this helps.

MID Servers and Clones - Support and Troubleshooting

 

A MID Server issues record for "User mid_user with mid_server role not associated with a MID Server....

Thanks for sending the links. These were helpful for troubleshooting from different perspectives but didn't really solve the solution. KB786475 came the closest with sys_metadata -> ecc_agent_sync_file -> ecc_agent_script_file details. 

We resolved the issue with a SN engineer on the call. We shared our midserver logs and it was identified that after upgrading the instance to Zurich Patch 3, 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:

Sal16
Tera Contributor

We are also encountering this same issue after going to zurich patch 3 on our test instance. I have verified credentials and connectivity. We have a dev mid server that moved to the same patch without issues. On the same day and configured the same way.