---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Resolving MID Server issues

# Resolving MID Server issues {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 Minuten Lesedauer

Troubleshoot problems with the MID Server to find solutions. Monitor the MID Server to
receive alerts about issues as they occur. Troubleshooting procedures exist to resolve specific
problems with the MID Server. The Knowledge Base on Hi contains several articles to help you
troubleshoot MID Server issues.

## Monitor the MID Server {#r_MIDServerTroubleshooting__section_qd3_4zt_yhb}

Monitoring a MID Server involves verifying entries in log files, confirming network
connectivity, and checking MID server status.

* If the MID Server is on a Windows host, navigate to the Windows Services console,
  locate the service name that matches the name that appears from the
  wrapper-override.conf file. If the MID Server process is the only
  Java process running on the host, monitor the memory used by java.exe and alert on less
  than the maximum configured memory defined in the
  \~\\agent\\conf\\wrapper-override.conf folder.

* Ensure that the agent0.log.0.lck file appears in the
  \~\\agent\\logs folder to confirm that the MID Server running and
  logging system activity in the agent0.log.0 file.

* Review the following logs for warning, critical, and severe errors:
  \~\\agent\\logs\\agent0.log.0
  \~\\agent\\logs\\wrapper.txt
  See [Manage ECC Queue content for a MID Server](https://servicenow-prod.fluidtopics.net/MiXcR9G3ui5Vkc~Z2ld0iQ#manage-ecc-queue-content "The ECC Queue allows you to create ECC Queue messages, access MID Server log entries, and retrieve statistics from an individual MID Server record.") to see
  how to open log entries from the instance.

* [Test MID Server connectivity](https://servicenow-prod.fluidtopics.net/p3M_8Z__2OtghiL5qiflyw "Confirm that the MID Server host is able to communicate with the instance. Resolve any issues with the network connectivity such as conflicts with firewalls, access control lists, and routing errors. Successful communication is necessary for automatic upgrades.")
  to confirm that the MID Server host is able to communicate with the instance. Resolve
  any issues with the network connectivity such as conflicts with firewalls, access
  control lists, and routing errors.

* From the MID Server instance, navigate to the MID Servers page,
  and review the status of the MID Server. For additional information, click a
  Name.

* Set up email, SMS, and push notifications to alert you when issues occur with MID
  servers. The MID Server Down notification is enabled by default.
  See [Notifications](https://www.servicenow.com/docs/access?context=notifications&version=australia&pubname=australia-platform-administration&ft:locale=en-US) for
  details.

{#r_MIDServerTroubleshooting__ul_brz_w21_b3b}

## Java Flight Recorder {#r_MIDServerTroubleshooting__section_gsq_f4h_hwb}

Java Flight Recorder (JFR) uses an articulate data model to analyze Java Virtual Machine
(JVM) internal and application specific memory usage and thread related details. On hosts
with Java 14 or later, Event Streaming enables analysis of specific JVM or application
events.

The JFR file actions Start JFR Recording, Stop JFR Recording, or Write JFR File, are accessed on the
instance in the MID Server's Related Links. By starting and stopping the JFR recording, you
can dump JFR data to the disk on demand. While JFR recording is on, you can write to the JFR
file from the MID Server instance page.

The JFR file is deleted by a scheduler to clean the data after 24 hours. This default
behavior can be overridden by adding the following configuration parameter in the
config.xml: `<parameter
name="mid.jfr.data.clean.interval" value="<time in milisec>"/>`

Custom JFR events can be written to JFR file. To disable event writing, add the following
configuration parameter to the config.xml: `<parameter
name="mid.jfr.record.aprobe" value="false"/>`

## Troubleshooting procedures {#r_MIDServerTroubleshooting__section_qc1_snd_thb}

The following procedures provide information on resolving specific problems with the MID
Server. Knowledge Base articles also cover a wide range of issues. If you are encountering
problems which are not covered in these procedures, search the Knowledge Base for related
articles. For instance, if you are experiencing symptoms such as the MID Server going down
or not responding, or CIs being duplicated during discovery, see [KB0597571](https://support.servicenow.com/kb_view.do?sysparm_article=KB0597571) for information and recommended solutions.  

[MID Server active issues](https://servicenow-prod.fluidtopics.net/3KggNfyrSD20Ih~6ZaMG8A "The ServiceNow instance has a dedicated table that publishes active issues with MID Servers and alerts administrators when a MID Server is in danger of exceeding its resources.")
:   The ServiceNow® instance
    has a dedicated table that publishes active issues with MID Servers and alerts
    administrators when a MID Server is in danger of exceeding its resources.

[Active MID Server post-cloning credential issues](https://servicenow-prod.fluidtopics.net/___PADb6rsysMMQODK4aWA "The system provides automatic processes to detect and notify you of possible MID Server credential issues after instance cloning.")
:   The system provides automatic processes to detect and notify you of possible MID
    Server credential issues after instance cloning.

[MID Server resource threshold alerts](https://servicenow-prod.fluidtopics.net/~rzR0QsaqHHurYouZQvhRw "The instance displays warnings when a MID Server breaches its resource thresholds for CPU and JVM memory usage, enabling users to create email notifications or custom scripts when a breach occurs.")
:   The instance displays warnings when a MID Server breaches its resource thresholds
    for CPU and JVM memory usage, enabling users to create email notifications or custom
    scripts when a breach occurs.

[MID Server user connectivity issues](https://servicenow-prod.fluidtopics.net/7pRJr8OLo7pVjd8Jpfnslw#mid-server-connectivity-issues "The instance writes issues involving MID Server user logins and network connectivity to the MID Server Issue [ecc_agent_issue] table and creates events you can use in custom scripts or to send email notifications.")
:   The instance writes issues involving MID Server user logins and network connectivity
    to the MID Server Issue \[ecc_agent_issue\] table and creates events you can use in
    custom scripts or to send email notifications.

[Interpreting MID Server user debugging output](https://servicenow-prod.fluidtopics.net/m1jy71AOQnk21LaSQ45irA "Debugging output from the system log is available in either a summary or detailed view for MID Server user issues, but must be enabled manually.")
:   Debugging output from the system log is available in either a summary or detailed
    view for MID Server user issues, but must be enabled manually.

[MID Server Upgrade History](https://servicenow-prod.fluidtopics.net/pxoe2DmwwFJ~McdQ5jrshg "Use this module to troubleshoot errors that occur during the MID Server upgrade process. The MID Server Upgrade Histories table contains a record of each instance upgrade. The MID Server Upgrade Stages table shows the status of each MID Server and its upgrade progress, including any errors encountered.")
:   Use this module to troubleshoot errors that occur during the MID Server upgrade
    process. The MID Server Upgrade Histories table contains a record of each instance
    upgrade. The MID Server Upgrade Stages table shows the status of each MID Server and
    its upgrade progress, including any errors encountered.
* **[MID Server active issues](https://servicenow-prod.fluidtopics.net/3KggNfyrSD20Ih~6ZaMG8A)**   
  The ServiceNow® instance has a dedicated table that publishes active issues with MID Servers and alerts administrators when a MID Server is in danger of exceeding its resources.
* **[MID Server fails to start](https://servicenow-prod.fluidtopics.net/lrUKi_DbtHAa3kCUdBmRdg)**   
  When a newly installed MID Server fails to start or shuts down prematurely, improper configuration could be to blame.
* **[Active MID Server post-cloning credential issues](https://servicenow-prod.fluidtopics.net/___PADb6rsysMMQODK4aWA)**   
  The system provides automatic processes to detect and notify you of possible MID Server credential issues after instance cloning.
* **[MID Server resource threshold alerts](https://servicenow-prod.fluidtopics.net/~rzR0QsaqHHurYouZQvhRw)**   
  The instance displays warnings when a MID Server breaches its resource thresholds for CPU and JVM memory usage, enabling users to create email notifications or custom scripts when a breach occurs.
* **[MID Server user connectivity issues](https://servicenow-prod.fluidtopics.net/7pRJr8OLo7pVjd8Jpfnslw#mid-server-connectivity-issues)**   
  The instance writes issues involving MID Server user logins and network connectivity to the MID Server Issue \[ecc_agent_issue\] table and creates events you can use in custom scripts or to send email notifications.
* **[Interpreting MID Server user debugging output](https://servicenow-prod.fluidtopics.net/m1jy71AOQnk21LaSQ45irA)**   
  Debugging output from the system log is available in either a summary or detailed view for MID Server user issues, but must be enabled manually.
* **[MID Server Upgrade History](https://servicenow-prod.fluidtopics.net/pxoe2DmwwFJ~McdQ5jrshg)**   
  Use this module to troubleshoot errors that occur during the MID Server upgrade process. The MID Server Upgrade Histories table contains a record of each instance upgrade. The MID Server Upgrade Stages table shows the status of each MID Server and its upgrade progress, including any errors encountered.

**Zugehörige Konzepte**   

* [MID Server upgrades](https://servicenow-prod.fluidtopics.net/FHThP3zPMJs8jJC1nxVqog "Upgrade MID Servers manually, or automatically through the instance. MID Server automatic upgrade is triggered when the instance upgrades and the MID Server no longer has the same version. The new MID Server package is downloaded from install.service-now.com, replaces the old one, and the MID Server starts with the new version.")
* [MID Server dashboard](https://servicenow-prod.fluidtopics.net/MYHGRvRY22woR5yJ4ojrAg "The MID Server dashboard is a central place for MID Server users to monitor ongoing operations. The dashboard consists of reports and gauges that display information from the MID Server Status table.")
* [MID Server File Cleaner](https://servicenow-prod.fluidtopics.net/GpXSjvTBt1RCnM1fQpg3Qw "A monitor thread runs in the MID Server to clean up old files, to keep the size and quantity of files within the install folder manageable, and to prevent performance issues with the MID Servers.")
* [MID Server privileged commands](https://servicenow-prod.fluidtopics.net/wiZ0usMr7e9KjcSsNjCZIQ#c_PrivilegedCommandsForMIDServer "To discover certain information on a host server, the MID Server must run SSH commands with higher privileges. The platform provides default privileged commands for the MID Server to use and the ability to add additional commands to the system.")  
**Zugehörige Tasks**   

* [Manually start, stop, and restart a MID Server](https://servicenow-prod.fluidtopics.net/xnuvo9vYRDPE6l8~h5dlUA "If you did not start the MID Server at the end of the installation procedure, you can manually start the MID Server.")
* [Set the MID Server JVM memory size](https://servicenow-prod.fluidtopics.net/rVu6TD9zQbdsIOlZ5i18YQ "The MID Server starts with a default JVM memory allocation, but you can modify this setting in the configuration file.")
* [Pause the MID Server](https://servicenow-prod.fluidtopics.net/gge75dsElgGaBRUdzpAzjg#t_PauseTheMIDServer "Pause the MID Server to temporarily prevent it from polling the ECC Queue for work or sending Discovery results back to the instance.")  
**Zugehörige Verweise**   

* [MID Server system requirements](https://servicenow-prod.fluidtopics.net/cz~U8SBK9UwjNYMyKIBxOA "Use these minimum system requirements to allocate resources for computers hosting MID Servers.")
* [MID Server properties](https://servicenow-prod.fluidtopics.net/QaGrUhy3s9geVRy_yTSrWQ#r_MIDServerProperties "Properties control the behavior of all MID Servers or a particular MID Server.")
* [MID Server parameters](https://servicenow-prod.fluidtopics.net/VYH5xHLIPq1GhC9qbQDc9Q#mid-server-parameters "Parameters control the behavior of a particular MID Server and have lower precedence than MID Server properties.")
* [MID Server Configuration Parameter settings and priority](https://servicenow-prod.fluidtopics.net/PqP96ecRuYupotmsL6tyKQ "The MID Server's settings reside in multiple tables and the MID Server prioritizes them in a set order. MIDConfigParameter must be defined with the correct type-style builders.")
* [MID Server protected records and reserved characters](https://servicenow-prod.fluidtopics.net/9Qj46OIDTGN0kXwwYX6gxQ "Some MID Server records cannot be altered. Certain special characters are pre-defined in XML and cannot be used in passwords.")
* [MIDSystem methods](https://servicenow-prod.fluidtopics.net/mM3TQJTR~rr6IghVfilArg "MIDSystem variables (referred to by the variable name ms.) provide a variety of methods to get information about the MID Server.")
* [MID Server heartbeat](https://servicenow-prod.fluidtopics.net/iyiaCdK4VdUNvsARghYGaA "The instance checks the MID Server for a response every 5 minutes, using a synthetic transaction monitoring system.")

