I'm using SQL Developer 4.1.2 and trying to connect to SQL Server using Windows authentication. If I use SQL Server authentication, everything works so the jTDS driver appears to be installed and working correctly (I'm using jTDS 1.2). When I switch over to Windows authentication, I get the error
Status : Failure -Test failed: I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property.
Of course, I Googled the error and came up with dozens of people asking the same question and getting told to move the ntlmauth.dll from the \SSO directory in the jTDS directory into various other directories. That seemed to work for others so for the past few hours, I've been copying the DLL to every directory I can find anyone on the internet suggesting with no luck (I do restart SQL Developer each time). Within the SQL Developer directory, I tried
c:\Oracle SQL Developer 4.1.2.20.64\sqldeveloper
c:\Oracle SQL Developer 4.1.2.20.64\sqldeveloper\sqldeveloper\bin
c:\Oracle SQL Developer 4.1.2.20.64\sqldeveloper\jdk\jre\bin
On the off chance that something was still referencing a directory from a previous SQL Developer install, I put it in the same directories in the prior SQL Developer installs on this machine. On the theory that it was using the JVM from the machine rather than the one that I downloaded and installed with SQL Developer, I went ahead and dropped the DLL in the \bin directories for every Java install I could find on the system.
c:\Program Files\Java\jrd1.8.0_45\bin
C:\Program Files (x86)\Java\jre1.8.0_45\bin
C:\Program Files (x86)\Java\jre1.8.0_60\bin
Still no luck. From SQL Developer, I went to Help | About | Properties and verified that the first path in java.library.path is what I'd expect and where I dropped the ntlmauth.dll to start with. I even put it in c:\windows and c:\windows\system32 just to be extra safe.
| java.library.path | C:\Oracle SQL Developer 4.1.2.20.64\sqldeveloper\sqldeveloper\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS; |
Despite having the DLL roughly everywhere I can imagine I'd need to have it, I'm still getting the same error. I must be missing something obvious. But at this point I've been staring at it so long that I just can't see it.
Justin