SQL JDBC Connectivity Help

Question

SQL JDBC Connectivity Help

Adi N-210946

Newbie

Points: 1
More actions
February 22, 2005 at 9:04 am

#85105

I know this topic has been posted before but I've read everything I could get my hands on and still no luck. I just can't get rid of :
Got an exception!
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
On my SQL server side:
1) My Client Network Utility and Server Network Utility both have TCP enabled and default port set to 1433
2) I've set authentication to "SQL Server and Windows" instead of just "windows".
3) For now I'm using my 'sa' account as startup which is set to "SQL Server and Windows" authentication.
4) I've disabled and then enabled TCP a bunch of times, that doesn't seem to help.
5) My SQL Server log says:
2005-02-22 10:12:12.86 server SQL server listening on Shared Memory, Named Pipes.
It should say something about TCP according to the MS SQL help, but I've had no luck with that.
I've even tried NMAP on my computer to check for open TCP ports, and 1433 doesn't show up. My guess is the problem is with SQL Server 2000 (I'm using Java 1.5.0_01 for now). Is there some kind of trick (ritual? animal sacrifice?) needed to get SQL Server to start listening on TCP?. Please...I'm at my witsd end and any help in the matter would be GREATLY appreciated. Thanks

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

James Weaving SSC-Addicted Points: 423 More actions · Answer 1

Have a look at the following MS knowledge base article, this suggests that you need to install the latest service pack to fix this but does give a workaround in case this can't be done for some reason.

http://support.microsoft.com/default.aspx?scid=kb;en-us;308766

Hope this helps.

Regards,

James

Vikash Anil Valued Member Points: 74 More actions · Answer 2

I am also getting the same error:

Exception in thread "main" java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.

at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source

)

at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)

at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)

at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Sou

rce)

at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown S

ource)

at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)

at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)

at java.sql.DriverManager.getConnection(DriverManager.java:512)

at java.sql.DriverManager.getConnection(DriverManager.java:171)

at Test.main(Test.java:8)

I am try to connect to the Local SQL sever on the same box. Also disabled the Wondows firewall. Also tried running with following policy.

grant {

permission java.security.AllPermission;

permission java.net.SocketPermission "*.microsoft.com:0-65535", "accept, connect, listen";

permission java.io.FilePermission "C:\\TEMP\\-", "read,write,delete";

};

Using Win XP SP2, SQL 2K SP3a, MS JDBC Driver SP3. But always getting the same error. Please Help!!!

MVDBA (Mike Vessey) SSC-Insane Points: 21797 More actions · Answer 3

has anyone come up witha fix for this yet ?

I'm getting a similar error - although this is only happening when not using connection pooling.

It appears that connections are not being closed and we get no sockets available for connection.

MVDBA