Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] trouble connecting with MSSQL with JAVA Talend

hi,
i need to connect to MSSQL using NT AUTHENTICATION (no username or password)
i receive the following message when i try to test the connection:
I/O Error: SSO Failed Native SSPI library not loaded. Check the java.library.path system property.
where do i get started to solve this one?
i understand that it is not a solely Talend problem, but i have not found a solution in java related forum (i am not searching for the right thing)
thanks,

Nicolas
Labels (2)
15 Replies
_AnonymousUser
Specialist III
Specialist III

Hi
Just forgot to mention that I tried x32 and x64 talend launchers.
regards

Hi,
I have the same problem. Does somebody found a solution in the meantime?
regards
E.
Anonymous
Not applicable
Author

Hi
Maybe you could find the solution in the following link:
http://jira.talendforge.org/browse/TDI-18787
Best regards
Shong
_AnonymousUser
Specialist III
Specialist III

I added information in the Additional parameters box: user=<USR>;password=<PWD>;domain=<DOMAIN> and it seems to work. I'll go back to sleep...
_AnonymousUser
Specialist III
Specialist III

Hi All,
I downloaded the folder and placed the Dll files in two places as mentioned I closed talend and relaunched again I was able to connect using windows authentication but after some time I was not able to again.
help required.
Thanks
Sri
_AnonymousUser
Specialist III
Specialist III

The suggested locations above (in the JDK bin, in the JRE bin, in system32) for ntlmauth.dll did not work for me on Windows 7 Pro x64 running the 64-bit TOS on a 64-bit JVM.
I even added a simple little Java component:
System.out.println(System.getProperty("java.library.path"));

...and that included the attempted locations, taken from the system PATH as expected.
However, placing ntlmauth.dll in the root of TOS (same folder as TOS_DI-win-x86_64.exe) made it work. I have an acceptable workaround, but if anybody knows why the other java.library.path locations don't work, I'm curious to know.
alevy
Specialist
Specialist

For an exported job, ntlmauth.dll can be placed in whatever is the "current directory" when java.exe is called. Since the standard batch file to launch a job changes the current directory to the location of the batch file before calling java, place the DLL in the same folder as the batch file.