Data source connection failed: cannot reach JDBC or LDAP source

MID Server is down, unreachable, or not properly configured for the data source connection. The MID Server may have stopped running or lost network connectivity to ServiceNow or the target system. (high likelihood)

Invalid or expired credentials configured in the data source definition. Username, password, or authentication certificates may be incorrect or have been changed in the target system. (high likelihood)

Network connectivity issues between the MID Server and the external JDBC database or LDAP server, including firewall blocks, DNS resolution failures, or port accessibility problems. (medium likelihood)

Target database or LDAP server is unavailable, overloaded, or experiencing service interruptions. The external system may be down for maintenance or experiencing performance issues. (medium likelihood)

Incorrect connection parameters in the data source configuration such as wrong server URL, port number, database name, or LDAP base DN settings. (low likelihood)

Step 1: Navigate to MID Server > Servers and verify the MID Server status shows as Up and the last refreshed time is recent. If down, restart the MID Server service on the host machine.

Step 2: Check the MID Server logs on the host system in the logs directory for connection errors or authentication failures. Look for specific error details about the failed connection attempt.

Step 3: Navigate to System Import Sets > Administration > Data Sources and open the failing data source. Verify all connection parameters including server URL, port, database name or LDAP base DN are correct.

Step 4: Test the credentials by navigating to the data source record and clicking Test Connection. If authentication fails, update the username and password or verify certificate-based authentication is properly configured.

Step 5: From the MID Server host, test network connectivity to the target system using telnet or ping commands to verify the server and port are accessible. Check firewall rules if connection fails.

Step 6: Verify the target database or LDAP server is operational by connecting directly from the MID Server host using database client tools or LDAP browsers with the same credentials.

Step 7: Check the ECC Queue at System Diagnostics > ECC Queue for any related error messages that provide additional details about the connection failure.

Step 8: If using JDBC, ensure the appropriate database driver JAR files are present in the MID Server lib directory and restart the MID Server if drivers were added or updated.