We installed DB Connect to access a SQL Server database. We established a connection and can pull data using Splunk's GUI screens. We can see the database, tables, data... We are now attempting to access the SQL Server database using Splunk's DB Monitor jobs. When we run the Monitor, we get the messages below. Any ideas on what we are doing wrong? We turned a trace on the target SQL Server database and it doesn't even see the connection. I thought that if the GUI screen in Splunk was able to access the SQl Server DB, the DB monitor would also be able to. Any advice would be appreciated. splunk.dbx.monitor.DbmonException: Cancelling subsequent run of oneshot dump monitor (AUTO schedule) at com.splunk.dbx.monitor.impl.DumpDatabaseMonitor.performMonitoring(DumpDatabaseMonitor.java:35) at com.splunk.dbx.monitor.DatabaseMonitorExecutor.executeMonitor(DatabaseMonitorExecutor.java:124) at com.splunk.dbx.monitor.DatabaseMonitorExecutor.call(DatabaseMonitorExecutor.java:101) at com.splunk.dbx.monitor.DatabaseMonitorExecutor.call(DatabaseMonitorExecutor.java:36) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source ... View more