You are not logged in.
Announcement
Unanswered posts
|
here was my solution, i was using Windows 7 64bit - hope it helps
1. verify version of Talend that was installed via- Help -> About Talend Studio -> Installation Details
2. from same location verified version of Java that Talend was using, since i had both 6 and 7 installed.
3. Download jtds-1.2.6
4. Copy "jtds-1.2.6.jar"
FROM C:\Users\...\Desktop\jtds-1.2.6-dist
TO C:\Program Files\Java\jre7\lib
5. Copy "ntlmauth.dll"
FROM C:\Users\...\Desktop\jtds-1.2.6-dist\x64\SSO
TO C:\Program Files\Java\jre7\bin
6. Restarted PC
7. Set TCP port 1433 in SQL Server Configuration Manager under SQL Server Network Configuration -> Protocols for Server -> TCP/IP -> IPAll -> TCP Port (for some reason this was blank)
8. Added Additional parameters to connection setup:
“Integrated Security”=true
This is my connection for sql server authentication - I don't remember using anything different for Windows but we run from a Unix.
That would be interesting. Just a reminder that I'm using Windows Authentication (and not using SQL Server authentication). Outside of that I believe my setup is pretty generic. And would you also let me know what additional parameters you use. Good luck!
I tested 5.0.1 using an import from 4.2.3 from 4.0.1 and it was ok. I'll try to set up a new connection and see if mine works.
I was using TOS 5.0.1.
Which 5.x version were you using?
I tried the various suggestions with ntlmauth.dll and the jtds.jar file without success. So I figured I try an older version. Well, in less than 10 minutes I installed it and had a working connection.
I don't know what the problem is with the 5.x version but someone needs to figure it out. It seems fairly clear that Talend doesn't understand the root cause of the problem. Or perhaps no one uses MS SQL Server these days <wink!>.
I would again like to thank the people that offered the suggestions and support! It's awesome to see people helping each other out this way.
Craig
I've tested my connection using instance and sql server authentication at 5.0.1 and it was ok.
I had the same the problem with the TOS versions 4.2 and 5.0.
I think you should try with a version 4.1 of TOS, at least to see if your connection parameters are good.
janhess, thanks for your efforts. I'll be tied up the rest of today/tonight so it will be tomorrow before I can work more on this. I'll let you know as soon as I have had a chance to work more on it.
I wonder if this problem is limited to this component on Windows with SQL Server or if it's more widespread. It seems to be somewhat related to how the parameters are setup for the call to the jtds/jdbc driver. Hopefully I'll have a solution before much longer.
Regards,
Craig
Have you seen this?
http://www.talendforge.org/forum/viewto … ?pid=60754
Have you tried sql server authentication?
I found this on a forum on the web.
Copy the file 'jtds-1.2.2-dist\x86\SSO\ntlmauth.dll' from the unzipped JTDS --> <SQL Developer Home>\jdk\jre\bin. Then restart SQL Developer.
More progress (I think)...
If I use username and password, I get a "login failed" message.
Leaving them blank and using localhost results in a message I've seen on the forum.
Exception in component tMSSqlConnection_1
java.sql.SQLException: I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property.
I'll check with how others dealt with this and see the door finally opens.
Craig
Try localhost if this is on your machine and use username and password
This is some form of progress. Now I get a different message which suggests a connection might have occurred!
Exception in component tMSSqlConnection_1
java.sql.SQLException: Unable to get information from SQL Server: (local).
This gives me something different to try to figure out.
janhess, thanks for jumping in with your tip!
Craig