Troubleshooting MID Server Issues in ServiceNow: Key Things to Check

Understanding MID (Management, Integration, and Discovery Server) servers

Enrique Melendez

• 2 min read
Troubleshooting MID Server Issues in ServiceNow: Key Things to Check
Photo by imgix / Unsplash

When working with ServiceNow, you’ll often come across the term “MID Server.” But what exactly is it, and what is it used for?

Think of the MID Server (Management, Instrumentation, and Discovery Server) as a bridge. It facilitates communication between your ServiceNow instance and your local network or external services. Whether you’re running Discovery, Orchestration, or other integrations, the MID Server acts as the go-between, ensuring that data flows smoothly and securely.

Functions of a MID Server:

  1. Data Collection: The MID Server collects data from on-premises applications or devices and sends it to the ServiceNow instance.
  2. Orchestration: It can execute automated tasks within the local network.
  3. Discovery: It discovers hardware and software assets across the network.

These are things I checked that have helped me pinpoint a problems with MID servers:

  1. MID Server Status (The Service in the Host).
  2. MID Server status in the ServiceNow instance.
  3. MID Server logs for errors or warning messages.
    1. Windows: `C:\ServiceNow\agent\logs\
    2. Linux: `/opt/ServiceNow/agent/logs/
  4. Connectivity: Ensure that the MID Server can ping the ServiceNow instance.
  5. Firewall: Check firewall settings to allow communication between MID Server and ServiceNow.
  6. Credentials: Verify the credentials used by the MID Server to connect to the ServiceNow instance.
  7. Proxy Settings: If the MID Server is behind a proxy, verify proxy settings.
  8. MID Server Configuration: Check MID Server configuration parameters in the ServiceNow instance.
  9. MID Server Version: Ensure that the MID Server version is compatible with the ServiceNow instance.
  10. ServiceNow Instance Health: Verify the health of the ServiceNow instance.
  11. MID Server Capacity: Check if the MID Server has sufficient resources (CPU, memory) to perform its tasks.
  12. MID Server Processes: verify that all necessary MID Server processes are running.
  13. ServiceNow Plugins: Ensure that any ServiceNow plugins related to MID Servers are installed and up-to-date.
  14. Job Queue: Check the ServiceNow job queue for any stuck or failed MID Server-related jobs.
  15. MID Server SSL Certificates: Verify SSL certificate configurations are in place and working as expected.
  16. MID Server Auto-Upgrade: If auto-upgrade is enabled, confirm that the MID Server is upgrading correctly or manually upgrade is necessary.
  17. Instance Timezone and Server Timezone.