This article is a starting point for troubleshooting MID server down issues: what the MID server status represents, where the MID server logs can be found, and troubleshooting MID server down.

MID Server Status

The MID server status is not an indication of whether the MID server service is running or stopped. Rather, the MID server status is a representation of the communication between the MID server and the instance. The MID server status is decided based on the last heartbeat input or ecc_queue record inputs received by the instance from a MID server. The scheduled job, or MID Server Monitor checks if a heartbeat input was returned after the last heartbeat output, or if any ecc_queue input was returned by the MID server within the last minute. The MID Server Monitor job calls the MonitorMIDServer script include. The MID server status is set to down if no heartbeat or ecc_queue input was received by the instance from the MID server. The MID server status is set to up the next time the MID Server Monitor job runs if any heartbeat or ecc_queue inputs were received from the MID server. Therefore, a MID server status may be set to down, even if the MID server service is running on the MID server host.

The MID server status may be set to down if:

  1. The MID server configuration file, agent/config.xml, has incorrect configuration such as invalid credentials, incorrect instance URL, or misconfigured proxy information
  2. The communication from the MID server to the instance is being blocked, which could be due to a proxy or a firewall
  3. The MID server service is not running, this could be caused by a manual stop or a crash of the MID server service

MID Server Logs

The MID server logs can be found under:


In the logs folder, there are two sets of log files:

  • agent.log
  • wrapper.log


Configuration File

Check Configuration File Parameters:

The configuration file, config.xml, is found under:


The following is part of an example MID server configuration file:

<!-- Tells the MID server where to contact its associated Service-now instance. Edit this value to provide the URL of your organization's Service-now instance. -->
<parameter name="url" value="https://YOUR_INSTANCE.service-nowcom"/>
<!-- If your Service-now instance has authentication enabled (the normal case), set these parameters to define the user name and password the MID server will use to log into the instance. -->
<parameter name="mid.instance.username" value="midserver"/>
<parameter name="mid.instance.password"  value="encrypted:AqSKti1xfos2IuWzkMQTFg==" encrypt="true"/>

Check that your configuration file does not have any typos for the parameters.

MID Server User Checks

Confirm configured user is not locked:

  1. On your servicenow instance, navigate to System Security > Users and Groups > Users
  2. Search for the user id configured as the mid.instance.usesrname, in this case we used midserver however your configuration file will likely have another user
  3. Check that the Locked Out box is not checked

Confirm user has the mid_server role:

  1. On the user record select the related list Roles
  2. Confirm the mid_server role is assigned to the user, assign the role is not

Check for authentication errors for the user:

  1. Navigate to System Logs > System Log > All and search for Basic authentication failed for user:
  2. If any basic authentication errors are found for the MID server user then the password may be incorrect

If the authentication errors are found perform either A or B as follows:

A– Update the password for the user to match what was set on the config file for the MID server. It may be best to reset the user password and then update the configuration file as the MID server encrypts the configuration file password. 

B– Update the password configured on the MID server service config file: 

  1. Navigate into the MID server and open <Installation_Directory>/config.xml, open with notepad on windows or vi if in linux, where <Installation_directory> is the location you installed the MID on.  
  2. Search for mid.instance.password.
  3. Replace the <parameter encrypt="true" name="mid.instance.password" value="encrypted:Old_Value"/> with <parameter encrypt="true" name="mid.instance.password" value="newpassword"/>.  
  4. In the previous step newpassword is the password for the account set for the MID server user.  
  5. The password will be re-encrypted once the service is restarted.  
  6. Restart the service. You need to do the above steps for each MID server service.  
  7. Give a minute and the MID server status should be updated to Up. 

Network Tests

Ping the instance from the MID server:

A ping confirms the instance can be reached from the MID server.

  • Log into the MID server host, open up the command prompt and run:

Note: Some environments may have ICMP requests disabled which could cause ping to fail.

Telnet to the instance:

If a ping is successful, then the instance can be reached from the MID server host. However communication on the port used to communicate to the instance may be closed. From the MID server command prompt:

telnet <ip_address> 443

 If the telnet test fails, an error message would be displayed, consult your network team to confirm:

  • There are no network firewalls blocking traffic from the MID server to the target host on the port tested

Log into instance:

From the MID server host, open up an internet browser an log into the instance. If login is successful from the browser, however the mid server still cannot communicate to the instance, compare the proxy settings used by the browser to the MID server proxy settings found in the configuration file.

Check IE proxy settings:

  1. Click Tools, then Internet Options
  2. Select the Connections tab
  3. Click on LAN Settings

When a browser is not available for testing, the command line may be used instead.


Open powershell and run:

PS C:\Users\Administrator> (Invoke-WebRequest -URI <url>).StatusDescription


From terminal run:

[user@Server]# curl -s -o /dev/null -w '%{http_code}' <instance_address>; echo "";

Check Service Status


The service status of a MID server installed on a windows host can be checked under windows services as follows: 

  1. Open windows server manager
  2. Click Tools and select Services
  3. Find the ServiceNow MID Server service
  4. Confirm its status is Running


The service can be confirmed to be running in linux by one of the following methods:

  • From the agent folder run the, ServiceNow MID Server is already running will be displayed if the service is already running
  • tail the MID server log to confirm output is being written
  • ps -ef | grep "agent/"

Review Logs:

If all tests are successful, and still the MID server is down, review the MID server logs for more information on why the MID server is down.

Release or Environment

All currently supported releases.

Article Information

Last Updated:2020-02-24 11:50:23