Error Reference

MID Server authentication failed: invalid credentials

MID Server authentication failed: invalid credentials

Where this appears

This error appears in the MID Server logs, ECC Queue records, and System Log under System Diagnostics > Log > Application Log. It occurs when a MID Server attempts to authenticate with the ServiceNow instance during startup, heartbeat validation, or when processing ECC queue records.

Sourdough
Chrome Extension

Debugging this in a real instance?

Sourdough lets you trace "MID Server authentication failed: invalid credentials" through system logs, script errors, and API health in the ServiceNow tab you are already using.

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview
Tasks
CMDB
API
Metrics
Monitor
Internals
Instance:sourdoughdev·Version:Yokohama
Instance StateONLINE
System StatusFully Operational
Session Timeout90 minutes
Logged-In Sessions2 (20 active)
Build Nameyokohama-12-18-2024_p1
IP Address10.159.128.43
Instance HealthHealth Score: 90%
🔥 5dSourdough (Chrome Plugin)Dark Mode

Cause

The MID Server service account password has expired or been changed in the ServiceNow instance without updating the MID Server configuration. (high likelihood)

The service account associated with the MID Server has been locked out due to multiple failed authentication attempts or security policies. (high likelihood)

The MID Server certificate has expired or is no longer trusted by the ServiceNow instance due to certificate authority changes. (medium likelihood)

Network connectivity issues or proxy authentication problems are preventing proper credential transmission between the MID Server and instance. (medium likelihood)

The MID Server user record has been deactivated, deleted, or assigned incorrect roles in the ServiceNow instance. (low likelihood)

Fix

Step 1: Navigate to MID Server > Servers in your ServiceNow instance and check the status and last contact time of the affected MID Server to confirm the authentication failure.

Step 2: Check System Log at System Diagnostics > Log > Application Log for detailed authentication error messages and review ECC Queue records for failed authentication attempts.

Step 3: Verify the MID Server service account exists and is active by navigating to User Administration > Users and searching for the MID Server user account.

Step 4: Reset the service account password in ServiceNow and update the mid.instance.password parameter in the MID Server's config.xml file with the new password.

Step 5: If the account is locked, unlock it in User Administration > Users, then check if account lockout policies need adjustment under System Security > Authentication.

Step 6: Verify the MID Server certificate validity by checking the certificate expiration date in the MID Server logs and regenerate certificates if expired using the MID Server certificate management tools.

Step 7: Restart the MID Server service after making configuration changes and monitor the System Log for successful authentication messages.

Step 8: Test connectivity by running a simple discovery or orchestration job to confirm the MID Server can authenticate and process requests successfully.

Test Your Knowledge

Quick 3-question quiz. See how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue