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.
Troubleshooting: How to resolve a MID Server returning multiple ECC Input records for one ECC Output record. - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Troubleshooting: How to resolve a MID Server returning multiple ECC Input records for one ECC Output record.
KB0716498

Troubleshooting: How to resolve a MID Server returning multiple ECC Input records for one ECC Output record.


684 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms

There may be times where you have strange behaviour when running any operation that utilises a MID Server. This can be characterised by double updates to records, Discovery not functioning correctly, or unexplained high CPU utilisation on a MID Server host. 

 

Possible Cause

This can be caused by multiple java.exe processes running under the context of the 'same' MID Server. 

To identify the issue, you can navigate to the MID Server record on the instance, and run a 'Grab logs'. If you get two sets of agent.log and wrapper.log ECC Inputs come back for one Grab Log, this is definitely the cause. 

Example Grab log: 

Remediation

If you see this, open Task manager and check that there are multiple java.exe running. If so:

  • Firstly restart the MID Server host. Sometimes when restarting a MID Server service, the old service fails to shut down properly, leaving a ghost java.exe process. This is easily resolvable by restarting the MID Server host.
  • After restarting, check in the Windows Services panel, and scroll down to "ServiceNow MID Server" xxxxx.
    • Check if there are multiple MID Server Services running, if so, see which two run from the same folder/file. Then set one to Startup type = disabled, then right click and stop one service.

This should ensure that only one MID Server service is running for one MID Server record. To verify the fix, you can do another Grab log on the MID Server record to ensure that only one set of logs are returned. 


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.