Feedback
Did this article resolve your question/issue?

   

Article

Can't connect to SQL Server using NTLM with the Connect for JDBC SQL Server driver

Information

 
TitleCan't connect to SQL Server using NTLM with the Connect for JDBC SQL Server driver
URL NameCan-t-connect-to-SQL-Server-using-NTLM-with-the-Connect-for-JDBC-SQL-Server-driver
Article Number000184289
EnvironmentProduct: Connect for JDBC SQL Server driver
Version: All supported versions
OS: JAVA
Database: SQL Server
Application: All supported applications
Question/Problem Description
Can't connect to SQL Server using NTLM with the Connect for JDBC SQL Server driver
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
URL contains the connect option LoadLibraryPath that was set incorrectly
Resolution
If using the connect option LoadLibraryPath, be sure it is set correctly. 

The driver looks for the DLL needed for NTLM authentication in a directory that is on the Windows system path defined by the PATH environment variable.  In this case if the DLL can be found there is no need to use the connect option LoadLibraryPath.

For additional information refer to the DataDirect Connect for JDBC User's Guide, DataDirect Drivers, Microsoft SQL Server, Connection Properties, "LoadLibraryPath"
Workaround
Notes
Last Modified Date3/21/2016 6:42 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.