---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/servicenow-platform

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Interpreting MID Server user debugging output

# Interpreting MID Server user debugging output {#ariaid-title1}

Release version: Australia  
Updated October 1, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Interpreting MID Server user debugging output

This guidance explains how ServiceNow customers can enable and interpret MID Server user debugging output to diagnose connectivity and authentication issues.
Debugging output is available in two formats---summary and detailed---and must be manually enabled on the instance.
The output helps identify problems related to MID Server user authentication, authorization, network connectivity, and configuration.
Show full answer Show less  

## Debugging Output Formats

* **Summary View:** Provides a high-level count of issues without naming specific MID Servers or users. Useful for quick assessment of problem scope.
* **Detailed View:** Lists specific users, their associated MID Servers, roles, and login activity. Enables in-depth troubleshooting of individual user and MID Server issues.

## Common Issue Types and Messages

* **Authentication Failures:** Display errors for users who cannot authenticate, indicating associated MID Servers that are down or missing. The detailed log names users and their MID Server status.
* **Authorization Failures:** Indicate users missing required roles despite having the `midserver` role. The detailed logs specify which users are affected and reference role deficiencies in event records.
* **Network Issues:** Occur when users associated with MID Servers do not attempt login within the configured reporting period, suggesting possible connectivity problems. This applies to both users with and without MID Server associations.
* **Configuration Issues:** Include users with the `midserver` role who are not associated with any MID Server or who connect successfully but may be misconfigured. These situations highlight potential role assignment errors or misuse.

## MID Server ID Map

The debugging output includes a mapping of MID Servers marked as Down to their user accounts, identified by the MID Server sysid. This map helps correlate user accounts with MID Server status, distinguishing between users associated with Down MID Servers and those not linked to any MID Server.

## Practical Use for ServiceNow Customers

* Enable debugging manually to obtain relevant connectivity issue data in the chosen format.
* Use summary output for quick identification of issue counts and detailed output for precise user-level troubleshooting.
* Reference error messages and MID Server mappings to pinpoint authentication, authorization, network, and configuration problems.
* Investigate associated event records to determine missing roles or other authorization failures.
* Adjust the sampling period to align with MID Server heartbeat intervals during detailed troubleshooting.

This diagnostic capability allows ServiceNow customers to efficiently identify and resolve MID Server user connectivity and permission issues, ensuring smoother MID Server operation and integration.  
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.
To enable debugging and display all connectivity issues in either of the available formats, you must run a method manually on your instance. For instructions on enabling debugging, see [Test remediation efforts for MID Server user connectivity issues](https://www.servicenow.com/docs/qhGO0sWBI0UeYSeVEZXpxg#debug-mid-connectivity-issues "After attempting to resolve a user connectivity issue that appears in the MID Server Issue [ecc_agent_issue] table, you can test your remediation efforts without having to wait until the next scheduled reporting period by shortening the sampling interval."). For information about each error condition and how records are created in the MID Server Issue \[ecc_agent_issue\] table, see [MID Server user connectivity issues](https://www.servicenow.com/docs/qhGO0sWBI0UeYSeVEZXpxg#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."). For information about debug parameters and setting debug logging, see [MID Server parameters](https://www.servicenow.com/docs/nf1LqohuHzOeBatmSwzyvQ#mid-server-parameters "Parameters control the behavior of a particular MID Server and have lower precedence than MID Server properties.").

## Available formats

You can configure the instance to generate a simple summary of the issue or a detailed output that identifies users and MID Servers. Summaries provide a quick look at the issue conditions, by count. The detailed view allows you
to examine roles, MID Server associations, and login activity by named users.  
In this summary example of an authorization issue, the instance evaluates each condition and indicates how many users met that condition. You can see that a MID Server is down and that one of two users configured for a MID Server failed authorization. Because this is a summary, neither the MID Server nor the users are named.Figure 1. Sample summary debug output

## Authentication failure

When a MID Server user cannot authenticate on the instance, the system displays these error messages in the detailed output:

* Login authentication failure for User \<user name\> associated with 1 down MID Server. Check password on MID server.
* Login authentication failure for User \<user name\> associated with \<n\> down MID Servers. Check password on MID servers.
* Login authentication failure for User \<user name\> with mid_server role not associated with a MID Server.
{#mid-user-connectivity-debug-output__ul_uts_brx_vy}

In this example, three users with the mid_server role, midserver2,
local-midserver, and ardis.maison, failed to
authenticate. Two of these users were configured for MID Servers that were
Down, and the other user was not configured for any MID Servers.
Each of these users has an authentication failure and is named in the appropriate error
message.  
Figure 2. Detailed debugging log for authentication failure

## MID Server ID map {#mid-user-connectivity-debug-output__section_sqr_xwr_rz}

The debugging output lists all MID Servers that are marked as Down
and maps them to their user accounts by the MID Server sys_id. This
map includes all user accounts that have the mid_server role, whether or not they are
associated with a MID Server. If there are no Down MID Servers, the
map is not displayed in the debugging output.  
The map is presented in three sections:

* User accounts not associated with any MID Servers.
* User accounts associated with Down MID Servers, identified by their sys_id.
* The sys_id of each Down MID Server, identified by name.

{#mid-user-connectivity-debug-output__ul_tzc_5zr_rz} Figure 3. MID Server ID map

## Authorization failure

If a user is missing any of the required roles, the instance generates these authorization failure messages:

* Login authorization failure for User \<user name\> associated with 1 down MID Server. Re-assign mid_server role to grant all required roles.
* Login authorization failure for User \<user name\> associated with \<n\> down MID Servers. Re-assign mid_server role to grant all required roles.
* Login authorization failure for User \<user name\> with mid_server role not associated with a MID Server.
{#mid-user-connectivity-debug-output__ul_ppq_11l_rz}

In this example, three users with the mid_server role, midserver2,
local-midserver, and ardis.maison have
failed authorization. One user is not associated with any MID Server, but the other two
users are. The system has logged an authorization failure, indicating that the user is
missing at least one critical role. To see what roles are missing, look at the comma
separated list in the Parm2 field in the
login.authorization.failed event record. This record is the most
recent login attempt in the Event \[sysevent\] table for the user account within the reporting
period.  
Figure 4. Detailed debugging log for authorization failure

## Network issues

Network issues may exist for these users who are associated with MID Servers, but who have not attempted to log in during the reporting period:

* User \<user name\> is associated with 1 down MID Server. No login attempts within reporting period.
* User \<user name\> is associated with \<n\> down MID Servers. No login attempts within reporting period.
{#mid-user-connectivity-debug-output__ul_jlz_2gp_qz}

Network issues may also exist for these users who are NOT associated with MID Servers, and
who have not attempted to log in during the reporting period: User \<user name\> with mid_server role is not associated with a MID Server. No login attempts within reporting period.  
In this example, no login attempts have been detected for midserver2, local-midserver, and ardis.maison, all of whom have the mid_server role. Two of those users are associated with MID Servers that are marked Down. The other user is not associated with any MID Server. None of these users has attempted to log in to the system within the configured reporting interval. The system assumes that these users would make an attempt to log in unless network issues prevented them from doing so.  
Note:  
By default, the sampling period is 4 hours. However, during debugging or remediation, the sampling period can be reset to a value that matches the MID Server heartbeat interval of 5 minutes, or greater.
Figure 5. Detailed debugging log for network connection issues

## Configuration issues

Any of the following messages can indicate a user configuration issue:

* Login authentication failure for User \<user name\> with mid_server role not associated with a MID Server.
* Login authorization failure for User \<user name\> with mid_server role not associated with a MID Server.
* User \<user name\> with mid_server role successfully connected but not associated with a MID Server. The mid-server role should be reserved for MID Server use only.
* User \<user name\> with mid_server role is not associated with a MID Server. No login attempts within reporting period.
{#mid-user-connectivity-debug-output__ul_elw_grj_yy}  
In this example, a user with the mid_server role has logged in successfully within the configured sampling interval. However, this user is not configured for a MID Server and might have the role in error. Figure 6. Detailed debugging log for MID Server user account login