Splunk DB Connect 2: Why am I getting "This driver is not configured for integrated authentication" trying to validate connection with my SQL database?

[Binway]

Hi All,

I have installed Splunk DB Connect 2 and am trying to connect to my SQL Server database. Both Splunk and SQL Server are running on my local machine. I followed the DB Connect 2 instructions and am trying to use the Windows Authentication process.

I have created an Identity and Connection, but when I validate the connection, I get the "Internal Server Error" message. I can read the log in Splunk by running the code index=_internal source=*dbx2.log and I get this message:

Validating connection with URL [jdbc:sqlserver://localhost:1433;databaseName=northwind;selectMethod=cursor;integratedSecurity=true] failed: java.sql.SQLException:java.sql.SQLException: Cannot create PoolableConnectionFactory (This driver is not configured for integrated authentication.

I am not sure what this means as I am certain I followed the steps to install the correct library so that it will use integrated authentication.

Any thoughts would be appreciated.

[avsnarayan]

Update PATH environment variable with folder location where sqljdbc_auth.dll is located.

After this you would observe another issue. Splunk would not pick right user name from the connection. In my case it picked [host name]$

SOLUTION
Use jTDS driver.
Download it from [jTDS][1].
Unpack the zip and copy jtds-1.3.1.jar to C:\Program Files\Splunk\etc\apps\splunk_app_db_connect\bin\lib
Restart splunk server

[1]: https://sourceforge.net/projects/jtds/files/,**SECOND :**
You should use jTDS driver to resolve this issue. Looks like Micorsoft Driver is not supported by Splunk for this scenario.

I tried it with good configuration but I observed splunk picking wrong user name and not the user name provided in the connections (splunk server host name) while connecting to SQL Server.

Download jTDS drivers from : https://sourceforge.net/projects/jtds/files/

Unzip the packages and place the jtds-1.3.1.jar in C:\Program Files\Splunk\etc\apps\splunk_app_db_connect\bin\lib

FIRST :
To resolve your error : Makesure that the PATH variable is set to folder where sqljdbc_auth.dll exists ( careful about x86 and x64).
After doing this, you would run into another issue as described above.

[nmohammed]

Thanks Avsnarayan, this solution worked fort me as well. Splunk DB connect is installed on a RHEL 6.7 server and was trying to connect to MS SQL server on Windows. the jTDS driver worked over the driver available from Microsoft (still giving errors).

[Binway]

hahaha yes indeed the sales rep would - god love 'em:)
Actually just a bit more on this, when i click the query tab in explorer from the validated connection I can run a query and display data from the database so i think this is good enough. DB Connect 2 is a little bit different to DB1 but I may be able to connect the query output to some lookups and so forth to "enrich" the data as i have done previously in DB1.
All good. Thanks.

[Binway]

Thanks for the info. I got past this issue by enabling the sql server sa account and changing from the " with windows authentication" driver to the one without. The connection now validates. Unfortunately I am using the "free" license and get the error in the log that says this license can't run "the requested action". So my demo tomorrow will not include a database connection part.
Thanks again.

[season88481]

Hi Binway,

I had a similar situation. Was using Windows authentication, but it didn't work. Then I try my luck by creating a new SA account. It works perfectly. Thank you.

Cheers,
Vincent

[acharlieh]

Splunk or SQL Server producing the error? If Splunk, I'm sure your sales rep would love to talk about a temp license for a demo. (If it goes well they could get sales)

[acharlieh]

There are a few different resources that seem to be related:

• https://answers.splunk.com/answers/234258/db-connect-2-connection-is-not-using-integrated-au.html
• http://blogs.msdn.com/b/jdbcteam/archive/2007/06/18/com-microsoft-sqlserver-jdbc-sqlserverexception-...