Cannot connect to SQL database

[nick405060]

Hi there,

I'm trying to connect to a MS-SQL server using DBConnect 2.4.1 and Splunk 6.3. I've been struggling with this problem for ages and could really use some help.

I had an error message in DBConnect saying that I needed to upgrade my JRE to JRE8 so I did that. Our network uses Windows authentication, so I'm using "MS-SQL Server Using MS Generic Driver and WinAuth," port 1433, and have tried sqljdbc4.jar and sqljdbc41.jar. With both drivers I get the error message:

com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: This driver is not configured for integrated authentication. ClientConnectionId:73024f75-db52-4eb4-83b4-0b6206645ffe 

Any suggestions? I have additionally tried many other driver/database connection options without any success. The database I'm trying to connect to is SCCM (yes I know there is an SCCM app but it is only compatible with Splunk 6.2). We have two SCCM servers, SCCM01 and SCCMSQL01 and so I'm trying to connect to SCCMSQL01.

[emam]

try creating local account on DB instead of windows authentication

[jwsmith22 · Accepted solution]

When debugging these issues, I usually use a third party Java SQL Client to test and white-box connections. Try to use Netbeans (https://netbeans.org/) with your driver to connect to your instances.

Also, on the message you are getting, you have probably seen: https://blogs.msdn.microsoft.com/psssql/2015/01/09/jdbc-this-driver-is-not-configured-for-integrated... , if not it may help.

[nick405060]

I had seen that page but was a bit confused because I am not using Linux whatsoever.

That being said, the fix was in the comment section. I copied sqljdbc_auth.dll to jre8/bin and jre8/lib, as well as to System32 and SysWOW64. One of those moves did the trick, probably the jre8/bin and jre8/lib moves from what I've read.

So, the article you posted answered the error message this question addresses. However, for robustness in case any future users run into a similar situation... even after I fixed the bug I was still having authentication problems with JDBC. I ended up getting it to work with jTDS as @Rob2520 suggested. Thanks to both of you!

[Rob2520]

Have you tried MS-SQL Server Using jTDS Driver With Windows Authentication? For windows authentication jTDS works much better. For this to work you got to check box windows authentication in identities and fill in domain name.

[jwsmith22]

jTDS hasn't had a release since 2013. It may be worth a shot, but that would concern me on a newer SQL Server instance.