# RESOLVED - MSSQL Server 2019 Connection Fails - This driver is not configured for integrated authentication **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [February 16, 2022, 3:08pm UTC](https://forum.inductiveautomation.com/t/resolved-mssql-server-2019-connection-fails-this-driver-is-not-configured-for-integrated-authentication/56211 "2022-02-16T15:08:07Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![reed.hoffmaster](https://avatars.discourse-cdn.com/v4/letter/r/ad7895/32.png) [@reed.hoffmaster](https://forum.inductiveautomation.com/u/reed.hoffmaster)\ **Post date:** [December 12, 2022, 7:52pm UTC](https://forum.inductiveautomation.com/t/resolved-mssql-server-2019-connection-fails-this-driver-is-not-configured-for-integrated-authentication/56211/5 "2022-12-12T19:52:27Z")
I also found that the filename that Ignition was looking for was not correct. My solution only requires the 9.4.0 file to be placed in the lib directory, and not the sqljdbc\_auth.dll file. > [@SQL Server Database Connection with Integrated Security](https://forum.inductiveautomation.com/t/sql-server-database-connection-with-integrated-security/2703/5): > > I was having trouble connecting with Windows Authentication as well. I found that I was getting a similar error from the Gateway Status page... Cannot create PoolableConnectionFactory (This driver is not configured for integrated authentication. I noticed further down in the stack trace however, that the driver version Ignition was looking for did not match the latest version I downloaded (per the User Manual Guide: [Connecting to Microsoft SQL Server](https://docs.inductiveautomation.com/display/DOC81/Connecting+to+Microsoft+SQL+Server), Scenario 2: Connect By Using Instance Name… --- _[View the full topic](https://forum.inductiveautomation.com/t/resolved-mssql-server-2019-connection-fails-this-driver-is-not-configured-for-integrated-authentication/56211)._