In Splunk DB Connect version 3.16.0, the mssql_jtds_win_auth connection type—used for "Microsoft SQL Server with Windows Authentication via the jTDS driver "—is no longer supported. Attempting to configure or validate a connection using this type causes a failure with errors in the logs.
This issue arises because the jTDS driver is deprecated and removed from compatibility in DB Connect 3.16.0 and later. The application fails to resolve the necessary connection URL, making the configuration unusable.
While saving a connection using the deprecated driver, the following error appears in the logs:
SPL :
index=_internal sourcetype=*dbx* "Error" "connection_name"
Error log :
2025-05-12 09:13:24.134 -0500 Trace-Id=fdb485fd-08b2-4acb-a54f-8459a44f71eb [dw-122894 - POST /api/connections/status] ERROR c.s.d.s.a.s.d.impl.DatabaseMetadataServiceImpl - action=error_in_validating_connection connection=ConnectionConf{connectionType='mssql_jtds_win_auth', ...}
java.lang.IllegalStateException: UrlFormat is null, ConnectionConf is not fully resolved, name: ****
Splunk DB Connect v3.16.0 removes support for the jTDS driver. The mssql_jtds_win_auth connection type no longer resolves correctly, resulting in incomplete configuration and failure during validation.
Kindly follow the below steps to mitigate the issue:
Install JDBC Add-on
Install the Splunk DBX Add-on for Microsoft SQL Server JDBC.
Reload Drivers
Go to Apps > Splunk DB Connect > Configuration > Drivers and verify the Microsoft JDBC driver is loaded.
Create New Connection
Create a new connection using:MS-SQL Server Using MS Generic Driver With Windows Authentication
Provide necessary details including host, port, domain, and credentials.
Test and Save
Refer to the Splunk DB Connect 3.16.0 Release Notes for official deprecation details of the driver.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |