topic Re: tMSSqlConnection frustation! in Talend Studio

tMSSqlConnection frustation!

Anonymous — Sat, 16 Nov 2024 12:22:27 GMT

I'm out of ideas on how to get the tMSSqlConnection to connect to my SQL Server 2008 R2 database. This seems like it should be easy but for me it's been a humbling exercise in futility. Sure hope some can point out something I've overlooked.
Let me start with the typical error message:
Exception in component tMSSqlConnection_1
java.sql.SQLException: Network error IOException: Connection refused: connect
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:410)
TOS version: 5.0.1
Component basic config: Host: "127.0.0.1", Port: "1433", Schema: "dbo", Database: "QHR", Username: "MyUsername" Password: "MyPassword"
SQL Server 2008 R2: Windows Authentication, IP addresses enabled, Dynamic port, Remote connections allowed
Variations I've tried:
Host: "SQLR2" (the instance name), "(local)", "(localhost)", "192.168.10.20" (LAN IP address), "Servername\\SQLR2".
Port: (a different port number that was matched with a static port number on SQL Server side.)
Schema: (out of desperation tried "", but nothing else)
Username: tried blank usernames, tried blank username after adding NTLMAUTH.DLL (from jTDS 1.2.5) for Windows Authentication / SSO
Password: (same as for Username above)
Microsoft Firewall: enabled & disabled
I have also tried connect with named pipes after enabling this on SQL Server. I get the following error:
Exception in component tMSSqlConnection_1
java.sql.SQLException: Network error IOException: \\(local)\pipe\sql\query (The network path was not found)
I have no problem connecting with SQL Server Management Studio, SQL query tools, or Tableau (a data visualization app that can make MS SQL connections).
My system is running Windows 7 Professional with all patches & updates.
Cheers,
Craig

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 06:50:31 GMT

Hi Craig
This is a common issue about SQL SERVER 2008 Installation in Win7.
Check whether TCP/IP protocal has been started up in SQL SERVER Configure Manager.
Regards,
Pedro

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 06:55:39 GMT

I had done that but I neglected to note this in my describing my other misadventures. Thanks for the suggestion though!
Craig

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 06:57:33 GMT

Hi Craig
Now I think this is an issue at MSSQL side...
Regards,
Pedro

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 07:03:28 GMT

You could be correct. I'm torn between thinking it has something to do with the jdbc driver/component configuration and a networking issue. However, the fact that other programs can access the database tilts me towards the jdbc driver/component configuration (maybe somehow related to Windows Authentication for SQL Server).
I didn't mention it but I've also checked to make sure that TOS is using a direct connection (no proxy), which some users found to be a problem.
I appreciate your suggestion!
Craig

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 07:14:39 GMT

Hi Craig
Is MSSQL mixed auth mode(means both sqlserver auth mode and windows auth mode)?
Regards,
Pedro

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 07:36:10 GMT

The database was installed to use Windows Authentication. I made a couple of attempts to reconfigure SQL Server for mixed mode, but I had similar connection issues and I was reluctant to leave SQL Server running in mixed mode so I undid those changes.
I never thought I'd spend an entire day just getting the connection working, especially since the options all seem pretty basic. I must be overlooking something simple, but I haven't been able to figure it out yet.
Craig

Re: tMSSqlConnection frustation!

Spretorius — Thu, 16 Feb 2012 07:44:41 GMT

Hi Craig
For windows authentication the username and password should be left blank in talend.
And then you should also have the ntlmauth.dll in the windows\system32 folder.
I had the same problem before and this worked for me. So hope this will be able to help you.
Regrds,

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 08:00:48 GMT

Based on the reports of others, maybe even you own report, I was hopeful that the NTLMAUTH.DLL would be the secret sauce but I didn't see any change. I used the 64-bit dll and put it in \windows\system32. I didn't reboot, which I'm wondering now if that would have helped in case the dll doesn't get unloaded.
I also tried the current version of the jtds.jar file (this is the java driver that Talend uses). Talend ships with 1.2 and the current version is 1.2.5. I figured I had nothing to lose by trying but I couldn't tell any difference with this change either. Again, if a jar update requires a restart, then I might have to redo this.
Oh, btw, thanks for your suggestion, too!
Craig

Re: tMSSqlConnection frustation!

janhess — Thu, 16 Feb 2012 09:07:20 GMT

Do you use instances?

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 15:14:56 GMT

The SQL Server instance name is SQLR2; however, I don't see a field for entering the instance name. Where would this go?
Craig

Re: tMSSqlConnection frustation!

janhess — Thu, 16 Feb 2012 16:04:45 GMT

In Additional JDBC parameters put "instance=SQLR2"
I think you will need username and password as well.

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 16:07:53 GMT

Cool, I'll give it a try. Got my fingers crossed! Will let you know how it turns out.
Craig

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 16:14:06 GMT

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

Re: tMSSqlConnection frustation!

janhess — Thu, 16 Feb 2012 16:23:22 GMT

Try localhost if this is on your machine and use username and password

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 16:53:57 GMT

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

Re: tMSSqlConnection frustation!

janhess — Thu, 16 Feb 2012 16:58:59 GMT

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.

Re: tMSSqlConnection frustation!

janhess — Thu, 16 Feb 2012 17:02:48 GMT

Have you seen this?
http://www.talendforge.org/forum/viewtopic.php?pid=60754

Re: tMSSqlConnection frustation!

Anonymous — Thu, 16 Feb 2012 18:53:25 GMT

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

Re: tMSSqlConnection frustation!

Anonymous — Fri, 17 Feb 2012 09:04:38 GMT

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.