Service Graph Connector Test 20 load records error

[Joshua Comeau]

Getting the following error when trying to load the data source any ideas?

MID Server reported error: SQLState: null

java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: Read timed out ClientConnectionId:

com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2924)

com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:2029)

com.microsoft.sqlserver.jdbc.SQLServerConnection.Prelogin(SQLServerConnection.java:2635)

com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2480)

com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2142)

com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1993)

com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1164)

com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:760)

java.sql/java.sql.DriverManager.getConnection(DriverManager.java:677)

java.sql/java.sql.DriverManager.getConnection(DriverManager.java:189)

com.service_now.mid.connections.jdbc.JDBCConnection.establishConnection(JDBCConnection.java:153)

com.service_now.mid.connections.jdbc.JDBCConnection.lambda$connect$0(JDBCConnection.java:110)

com.glide.util.LogContext$Frame.run(LogContext.java:212)

com.service_now.mid.connections.jdbc.JDBCConnection.connect(JDBCConnection.java:108)

com.service_now.mid.connections.jdbc.JDBCConnectionFactory.create(JDBCConnectionFactory.java:72)

com.service_now.mid.connections.ConnectionCachePool.getAvailableConnection(ConnectionCachePool.java:83)

com.service_now.mid.connections.ConnectionCache.get(ConnectionCache.java:95)

com.service_now.mid.probe.JDBCProbe.getJDBCConnection(JDBCProbe.java:951)

com.service_now.mid.probe.JDBCProbe.probe(JDBCProbe.java:219)

com.service_now.mid.probe.AProbe.process(AProbe.java:155)

com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:131)

com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20)

com.service_now.mid.threadpool.ResourceUserQueue$RunnableProxy.run(ResourceUserQueue.java:640)

java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

java.base/java.lang.Thread.run(Thread.java:829)

at com.service_now.mid.probe.JDBCProbe.getJDBCConnection(JDBCProbe.java:955)

at com.service_now.mid.probe.JDBCProbe.probe(JDBCProbe.java:219)

at com.service_now.mid.probe.AProbe.process(AProbe.java:155)

at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:131)

at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20)

at com.service_now.mid.threadpool.ResourceUserQueue$RunnableProxy.run(ResourceUserQueue.java:640)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:829)

[Ratnakar7 · Accepted solution]

Hi @Joshua Comeau ,

It indicates a timeout issue when trying to establish a connection to a Microsoft SQL Server database.
Here are some steps you can take to troubleshoot and resolve the issue:

1. Check the Database Connection Settings: Ensure that the connection settings in your ServiceNow instance are configured correctly. Verify the hostname, port number, database name, username, and password used to connect to the SQL Server database.

2. Verify Network Connectivity: Make sure that there are no network issues between your MID Server and the SQL Server database. Test the network connectivity by pinging the SQL Server from the MID Server machine.

3. Check SQL Server Configuration: Ensure that the SQL Server is configured to accept incoming connections from the MID Server. Verify the SQL Server configuration settings, including network protocols, firewall rules, and connection timeout settings.

4. Review MID Server Logs: Check the MID Server logs for any additional error messages or warnings that may provide more details about the issue. Look for any errors related to JDBC connections or SQL queries.

5. Increase Connection Timeout: If the issue persists, you may need to increase the connection timeout settings in your ServiceNow instance. This will allow more time for the MID Server to establish a connection to the SQL Server database before timing out.

6. Test Connectivity Outside ServiceNow: Try connecting to the SQL Server database from the MID Server machine using a standalone JDBC client or another tool to verify that the issue is not specific to ServiceNow.

Thanks,

Ratnakar