--- sourceDocument: Yokohama ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/servicenow-platform Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Resolving MID Server issues # Resolving MID Server issues {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Resolving MID Server issues This guide helps ServiceNow customers troubleshoot and resolve common issues with the MID Server. It covers monitoring techniques, identifying problems, and using built-in alerts and logs to quickly detect and address MID Server performance and connectivity issues. Understanding these procedures enables efficient MID Server management and minimizes downtime. Show full answer Show less ## Monitoring the MID Server * Check MID Server logs (agent0.log.0, wrapper.txt) for warning and error messages to identify problems. * Verify MID Server status from the MID Servers page in the ServiceNow instance and confirm connectivity between the MID Server host and the instance. * On Windows hosts, use the Services console to manage the MID Server service and monitor the Java process memory against configured limits. * Alerts such as **MID Server Down** notifications are enabled by default and can be configured to send email, SMS, or push notifications for real-time issue awareness. ## Java Flight Recorder (JFR) JFR allows detailed analysis of the Java Virtual Machine (JVM) and application memory usage and thread activity on MID Server hosts running Java 14 or later. * From the MID Server instance, users can start, stop, or save JFR recordings to gather diagnostic data on demand. * JFR files are automatically cleaned after 24 hours by default, but this interval can be customized via configuration parameters. * Custom JFR events can be disabled or enabled through specific configuration settings. ## Troubleshooting Procedures and Tools * Use Knowledge Base articles for detailed resolutions to common issues such as MID Server downtime or discovery problems. * The ServiceNow instance maintains a dedicated table for **active MID Server issues**, alerting administrators when resource limits are approached or breached. * Automatic detection and notification of credential issues after instance cloning help prevent connectivity failures. * Resource threshold alerts notify users of high CPU or JVM memory usage, enabling proactive management through notifications or scripts. * User connectivity issues and login problems are logged in the **eccagentissue** table, with events generated for custom handling. * Debugging output for MID Server user issues can be enabled manually, providing either summary or detailed logs for investigation. * The **MID Server Upgrade History** module tracks upgrade attempts and errors to assist with troubleshooting upgrade failures. ## Common Issues and Resolutions * **MID Server fails to start:** Often due to improper configuration; verify settings and logs to identify root causes. * **Post-cloning credential problems:** Automatically detected with alerts after instance cloning. * **Resource threshold breaches:** Alerts help prevent MID Server overload by notifying administrators when CPU or memory usage is excessive. ## Related Concepts and Tasks Customers can reference additional resources and perform related tasks such as manually starting, stopping, or restarting MID Servers, adjusting JVM memory size, pausing MID Servers, and reviewing system requirements and configuration parameters. These capabilities support comprehensive MID Server management and issue resolution. 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://www.servicenow.com/docs/ZMA0sg3NtYS3mj9dEjU8ew#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://www.servicenow.com/docs/8OWpo4hcPaopzeYbAWjaEQ "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=yokohama&pubname=yokohama-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: `` Custom JFR events can be written to JFR file. To disable event writing, add the following configuration parameter to the config.xml: `` ## 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://www.servicenow.com/docs/1dq1v31cxecby_AP2FmS3w "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://www.servicenow.com/docs/kWUmyjk8zQSvI~r6n16YYQ "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://www.servicenow.com/docs/PT1QtXTlxTxLGwlCPQ2NRw "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://www.servicenow.com/docs/k05Ug6ATKwFDaETXYJlchw#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://www.servicenow.com/docs/5CLnQ2G1bohk8SvC_p~8aQ "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://www.servicenow.com/docs/dnGwWIKRdou8_tuQm9q5lA "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://www.servicenow.com/docs/1dq1v31cxecby_AP2FmS3w)** 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://www.servicenow.com/docs/C0zeshuPd1dcg7j8_9CJiQ)** 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://www.servicenow.com/docs/kWUmyjk8zQSvI~r6n16YYQ)** 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://www.servicenow.com/docs/PT1QtXTlxTxLGwlCPQ2NRw)** 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://www.servicenow.com/docs/k05Ug6ATKwFDaETXYJlchw#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://www.servicenow.com/docs/5CLnQ2G1bohk8SvC_p~8aQ)** 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://www.servicenow.com/docs/dnGwWIKRdou8_tuQm9q5lA)** 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. **Related concepts** * [MID Server upgrades](https://www.servicenow.com/docs/0fmzqDHt0iEzymIrRBjJUA "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://www.servicenow.com/docs/CTke3Lqzsh8kfktMWhKK8A "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://www.servicenow.com/docs/UOs_PAj0ZzeS_1dGYhQ26A "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://www.servicenow.com/docs/jHZdSShGx_wDoFToSvoktw#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.") **Related tasks** * [Manually start, stop, and restart a MID Server](https://www.servicenow.com/docs/IYs5fBPqVEOuqstZJckkXw "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://www.servicenow.com/docs/KrWcjHIVVy4FOFmLc1ipGA "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://www.servicenow.com/docs/Q390rqi9OVkNNTzq97iJwA#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.") **Related reference** * [MID Server system requirements](https://www.servicenow.com/docs/4j~DXw_Cfdj1uyhyC10Muw "Use these minimum system requirements to allocate resources for computers hosting MID Servers.") * [MID Server properties](https://www.servicenow.com/docs/kCZI01CdDboQJ~Alkf3MFg#r_MIDServerProperties "Properties control the behavior of all MID Servers or a particular MID Server.") * [MID Server parameters](https://www.servicenow.com/docs/9bf6AMU0YzFSeKaPniMXlQ#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://www.servicenow.com/docs/zmIKyIToc_JohWVTG6CHNQ "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://www.servicenow.com/docs/R_UORSGTsWLLds5WDthYMg "Some MID Server records cannot be altered. Certain special characters are pre-defined in XML and cannot be used in passwords.") * [MIDSystem methods](https://www.servicenow.com/docs/8sGrXh3ukCa4vzdmJEPzVw "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://www.servicenow.com/docs/Cx2YLLAd_cUQAwGVk5QRIw "The instance checks the MID Server for a response every 5 minutes, using a synthetic transaction monitoring system.")