Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
System Log Error: *** Script: [ecc_agent_status] table record missing for MID Server mid_server_name : no thrown error - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • System Log Error: *** Script: [ecc_agent_status] table record missing for MID Server mid_server_name : no thrown error
KB0714755

System Log Error: *** Script: [ecc_agent_status] table record missing for MID Server mid_server_name : no thrown error


2072 Views Last updated : Jul 24, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

System Log Error will periodically throw these errors:

This is under System Logs>Errors and filter on message contains ecc_agent_status.  Note that em.sm.mid would be different a value or values in your case as this refers to MID Server name/s existing in your instance.

Release

All current supported releases up to London version.

 

Cause

There is a missing ecc_agent_status record in your instance.  For each MID Server existing in your instance, there should be one corresponding ecc_agent_status record. This record can be deleted or may not have been created for some reason or another.

The most likely cause is PRB1287729 related to Clone Exclude/Preserve settings, and so is usually see on sub-production instances.

Resolution

The recommended solution is to re-clone after upgrading to Madrid, or after implementing the workarounds in:
KB0688954 / PRB1287729 The MID Server Exclude/Preserve Clone settings cause MID Server issues on the target

If that is not possible at the time, Log in as admin in your instance and on filter navigation, enter ecc_agent_status.list. For each MID Server missing from the list, click "New" to create a new record and then enter the corresponding MID Server Name then save the record. The other fields will be automatically populated usually within 10 minutes.

Related Links

The ecc_agent_status record is created via out-of-the-box Business Rule "Insert into MID Server Status".  The Business Rule will create one ecc_agent_status record once a MID Server record is created in your instance. Check that the Business rule exists and is active.  In the MID Server>Dashboard.  The ecc_agent_status records are displayed in the top most widget.  Please refer to our product documentation for more information.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.