Error: java.sql.SQLException: No suitable driver found for sqlserverDescriptionWhen running a flow/action that uses a MID server to connect to a SQL server database, it fails with error shown below. 2024-06-12 12:12:43 ERROR (Worker-Expedited:IPaaSActionProbe-7114e27847fac25805308a37536d43e9) [JDBCConnection:184] java.sql.SQLException: No suitable driver found for sqlserver://db_server_name:db_port;selectMethod=cursor;databaseName=ABCjava.sql/java.sql.DriverManager.getConnection(DriverManager.java:702)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.snc.mid.jdbc.JDBCConnectionHandler.initJDBCConnection(JDBCConnectionHandler.java:52)com.snc.process_flow.operation.jdbc.MidJdbcExecutionWrapper.initializeConnection(MidJdbcExecutionWrapper.java:134)com.snc.process_flow.operation.jdbc.MidJdbcExecutionWrapper.execute(MidJdbcExecutionWrapper.java:114)com.snc.process_flow.operation.jdbc.MidJdbcExecutionWrapper.execute(MidJdbcExecutionWrapper.java:88)com.snc.process_flow.operation.JdbcOperation.executeOperation(JdbcOperation.java:78)com.snc.process_flow.operation.JdbcOperation.invoke(JdbcOperation.java:66)com.snc.process_flow.operation.RetryableIntegrationOperation.run(RetryableIntegrationOperation.java:61)com.snc.process_flow.engine.Operation.execute(Operation.java:207)com.snc.process_flow.operation.IntegrationOperation.execute(IntegrationOperation.java:56)com.snc.process_flow.restricted_caller_access.ExecuteWithoutCallerAccessTracking.executeWithMetaStack(ExecuteWithoutCallerAccessTracking.java:10)com.snc.process_flow.engine.ProcessEngine.executeOps(ProcessEngine.java:618)com.snc.process_flow.engine.ProcessEngine.runInternal(ProcessEngine.java:515)com.snc.process_flow.engine.ProcessEngine.resume(ProcessEngine.java:506)com.snc.process_flow.engine.ProcessAutomation.run(ProcessAutomation.java:99)com.snc.process_flow.engine.ProcessAutomation.run(ProcessAutomation.java:63)com.snc.process_flow.engine.ProcessAutomation.resume(ProcessAutomation.java:59)com.snc.process_flow.engine.MidProcessAutomation.resumeFlow(MidProcessAutomation.java:72)com.service_now.mid.probe.IPaaSActionProbe.lambda$probe$0(IPaaSActionProbe.java:129)com.glide.util.LogContext$Frame.run(LogContext.java:247)com.service_now.mid.probe.IPaaSActionProbe.probe(IPaaSActionProbe.java:99)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)Release or EnvironmentALLCauseThe connection URL in JDBC connection, used in the flow/action, is missing 'jdbc' prefix in it sqlserver://db_server_name:db_port;databaseName=ABCResolutionAdd 'jdbc' (shown in bold) prefix, as shown below in connection URL used by JDBC connection, in the flow/action jdbc:sqlserver://db_server_name:db_port;databaseName=ABC Additional InformationIt might happen with other databases as well, depending on connection URL used in JDBC connection/s. For information on creating JDBC connection/s, please review documentation shown below. https://docs.servicenow.com/csh?topicname=create-JDBC-connection.html&version=latest