Error establishing socket (Microsoft SQL Server 2000 Driver for JDBC)

I tray connect to MS-SQL2000 using JDeveloper and retrieve an error: "[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.[Microsoft][SQLServer 2000 Driver for JDBC]PC160832\NCI_DBA_01"
I followed the steps:
1 - Install the JDBC Driver for MS-SQL2000
2 - Create a new AddJavaLibPath :"AddJavaLibPath C:/Program files/Microsoft SQL Server 2000 Driver for JDBC/lib"
3 - Specify Default Project Libraries: "msbase.jar, msutil.jar and mssqlserver.jar"
4 - Create a new connection: "Java class name: com.microsoft.jdbc.sqlserver.SQLServerDriver" "URL: jdbc:microsoft:sqlserver://PC160832\NCI_DBA_01:1433;SelectMethod=cursor"
5 - Retrieve the error: "[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.[Microsoft][SQLServer 2000 Driver for JDBC]PC160832\NCI_DBA_01"

Were you able to resolve this? If so could you tell me how. I have the same problem.
Thanks!!!

Similar Messages

  • Regarding Microsoft SQL Server 2000 Driver for JDBC (2.2.0019)

    I have downloaded and installed Microsoft SQL Server 2000 Driver for JDBC (2.2.0019). Now i have to configure it for my development purpose. Can i use this driver for my development purpose or not. If yes does it create any kind of problem in future when i change the platform. My development should not depend on driver and database.
    Can i use any other driver provided by sun microsystem. If yes let me know where can i download and configure it.
    Waiting for the updates ASAP

    See, the bridge, being a type 1 driver has
    river has all the inherent limitations of that type
    drivers, due to the extra levels the data must
    passthrough inthe journey between the DB and the
    client. Also the use of native code.. makes it
    unsuitable to be used in applets.. the odbc should be
    configured in the client for this driver to work. etc.
    etc.
    It may be stable and useful for some
    for some applications.. but for sccenarios where one
    needs the solution tobe platform independent, ...By definition that would be the case. Of course the odbc-bridge does work on Windows, Solaris and Linux. So what other platform were you thinking about?
    ... less dependent on the user configuration,The bridge doesn't need any configuration. Or at least not any more than any other driver. The ODBC driver of course does need configuration.
    ...needs the minimum preparations from theuser, and above all give
    the fastest response time for him, the bridge cannot
    beat type 4 drivers. You are going to have to provide a link for that particular performance quote. Given that performance is impact most severely by requirements then design and finally by round trip time to the database I doubt that for applications (rather than benchmarks) that any difference is going to be significant.
    the problem i think was my use of
    my use of 'commercial' that u pointed out..
    anyway.. u are of course right if what u intended was
    stability only. but what i intended with that word was
    different .. sorry for creating the confusion.
    And it still seems like you are implying that it is not suitable for deployment in production systems. And as I pointed out I did deploy it in a large scale production system.
    I am not saying that type 4 drivers do not have a place nor that they do not have advantages, but their mere existance does not prove that they are a better choice for all installations.

  • SQL Server 2000 Driver for JDBC - Error establishing sockets

    Hi there
    I am using Microsoft SQL Server 2000 Driver for JDBC to connect to SQL Sever 2000. It is just a test application to see if it would connect to the datacase successfully. But I got the following errors. I already set up the classpath and installed all SQL Server 2000 Driver for JDBC sp 3. Dont know why it still failed...can anyone help me out of this? Thanks.
    When i am using simple JDBC-ODBC bridge Driver it's working fine.
    For this Server Pack3 , i have checked every thing like--
    TCP / IP Poart is Enable.
    I am working in client machine, my MSSQLServer 2000 Placed in server Machine.
    when i am giving Telnet ServerIP 1433 it's giving following response.
    connecting to ServerIP ....... could not open connection to the host , on port 1433:connection Failed
    My Sample Code is :--
    String user="sa";
    String password="imcindia";
    Connection con1 = null;
    CallableStatement cstmt = null;
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
    con1=DriverManager.getConnection("jdbc:microsoft:sqlserver://ServerName:1433;DatabaseName=dmo1o2d",user,password);
    Statement st=con1.createStatement();
    st.execute("use dm0102d");
    st.execute("setuser 'dm01012'");
    cstmt = con1.prepareCall("{?=Call dms_ex_create_folder('ABC','18753','NB21','u')}");
    cstmt.execute();
    Here are Error Code :
    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.base.BaseExceptions.getException(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
         at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
         at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
         at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
         at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
         at java.sql.DriverManager.getConnection(Unknown Source)
    java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Connection refused: connect
         at java.sql.DriverManager.getConnection(Unknown Source)
         at TestConnection1.main(TestConnection1.java:24)
    one can help me to over come this problm,
    Thanks in advance.
    venkat

    hey i also have this problem i have been looking for solution for this problem for along time i tried every possible solution i tried every service pack for the SQL but it didn't connect to the port!!!
    it's a network problem ur java code is correct dont worry about it.
    finally i had to install MySQL and it's work fine now but if u insist on usning SQL u have to use the JDBC-ODBC Bridge it will work by :
    first add data source database , follow these steps
    1- go to Administrative tools
    2-Data Sources(ODBC)
    3-System DNS tab and add then choose SQL SERVER the last option then finish
    4-write the name; Note: this name is the one that u will write in ur URL for example if u write Hello the URL will be "jdbc:odbc:Hello"
    5- choose the server, its recommended to write "." or (local)
    6-change the database to its an important step to choose the database that u want to use, choose northwind if u want to use it
    finish
    second
    adding this code:
    import java.sql.*;
    class JdbcTest1 { 
    public static void main (String[] args) { 
    try { 
    // Step 1: Load the JDBC driver.
    Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
    // Step 2: Establish the connection to the database.
    String url = "jdbc:odbc:Hello";
    Connection conn = DriverManager.getConnection(url,"user1","password");
    } catch (Exception e) { 
    System.err.println("Got an exception! ");
    System.err.println(e.getMessage());
    it will work without any problems

  • Error Establishing Socket with SQL Server 2000

    I have a java application that uses JDBC to connect to a source of data.
    The application has been installed on many platforms using many different data sources, but one combination has beaten me.
    I am using Windows Server 2003 and SQL Server 2000 Enterprise, when the application starts up it fails to connect to the database with the following message:
    [Microsoft][SQL Server 2000 Driver for JDBC] Error Establishing Socket
    I have looked at a lot of forums and tried many things but nothing has fixed the problem for me:
    To summarise:
    The URL I am using is jdbc:microsoft:sqlserver://locahost:1433
    I have also tried using the name of the machine and it's actual IP address
    I have checked that TCP/IP is enabled and using the correct port (1433)
    Both SQL Server and Windows authentication are enabled and I can connect using both method from ODBC
    I can connect to it and use it with c#.net, vb.net and ODBC from the same machine
    I have installed the latest SQL Server 2000 service pack
    The application works with SQL Server 2000 Developer on Windows XP
    If anyone has any other suggestions, I would love to hear from you.

    If you printed out the SQL state and error code that would be a bit more info:
    catch (SQLException e)
        e.printStackTrace();
        System.err.println("SQL state: " + e.getSQLState());
        System.err.println("SQL error: " + e.getErrorCode());
    }Maybe that will give you more detail as to exactly why this is happening.
    The only other thought I had was security. Maybe there's a permission to access the port that would have to be granted explicitly as part of M$'s new emphasis on security. You did say it was Windoze Server 2003. Maybe that's the difference between all the other installs and this one.
    No joy from me, sorry. - MOD

  • Problems! MS SQL Server 2000 Driver for JDBC.

    In Dos-promt ill got only this message: com.microsoft.jdbc.sqlserver.SQLServerDriver
    What is wrong and is there someone that can help me out?
    I have installed Microsoft SQL Server 2000 Driver for JDBC and set the path like this in the system, advance, environment variable:
    .;D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar
    This is the source code i use to test the connection:
    import java.sql.*;
    public class Exercise2_1 {
    static String driver = ("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    static String url= "jdbc:microsoft:MinTest;ah;modeerf";//sqlserver://H:1433;user=ah;password=modeerf";
    public static void main(String[] args) {
    try {
         Class.forName(driver).newInstance();
         System.out.println("Loaded driver");
         Connection conn = DriverManager.getConnection(url);
         System.out.println("Connected to database");
         conn.close();
         System.out.println("Closed connection");
    catch (Throwable e) { System.err.println(e.getMessage()); }

    You printed the error message associated with the exception but didn't print the type of the exception. com.microsoft.jdbc.sqlserver.SQLServerDriver was probably a ClassNotFoundException meaning that the VM couldn't find the jars.
    You say you put the jars in the path. They should actually be in the class path. Either set the CLASSPATH environment variable or pass it in to the Java VM via the -cp option.
    One more thing. Seeing as the paths that you installed the JDBC driver into contain spaces you may need to put quotes around the path names or use the MSDOS short names for those directories.
    Col

  • Error Using the SQL Server 2000 Driver for JDBC Service Pack 3

    Hi,
    I�m using the SQL Server 2000 Driver for JDBC Service Pack 3. The connection is succesfully, but when I use de statement.executequery() method, there is the follow exception:
    java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'PEC_COUNTRY'.
    This is my code:
    ResultSet resultSet;
    Statement statement;
    Connection connection;
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
    connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://S0MALMUERTA:1433;user=sa;password=");
    statement = connection.createStatement();
    resultSet = statement.executeQuery("SELECT COY_INX, COY_NAME, COY_ICO FROM PEC_COUNTRY
    ");When I make the last instruction, occurs the above exception
    Thanks in advance
    Luija

    The way you are connecting, the default database used will be 'master' and i guess that the table PEC_COUNTRY was defined in another database.
    If it is the case you need to specify the database name.
    connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://S0MALMUERTA:1433;DatabaseName=yourdb;user=sa;password=");

  • Intermittent error establishing socket on SQL Server 2000

    I have a suite of 130 JUnit tests. Recently, they started to give me intermittent "error establishing socket" errors when trying to connect to a local instance of SQL Server 2000 via JDBC.
    Each test creates one or more connections. I've used wrappers to prove that I'm closing all of the connections, statements, prepared statements and result sets. The first 70 or 80 tests succeed. After that every test gets the "error establishing socket" exception. Sometimes (but not always) SQL Server continues to refuse connections when I re-run the suite. When that happens I have to let it sit for 30 seconds or so (or restart the server) before it will accept connections.
    I've tested this with both Microsoft's and WebLogic's JDBC drivers with the same results. There's nothing in the SQL Server logs when this happens. There's nothing in the Windows event logs, either.
    If I sleep for 5 seconds between each test the problem goes away.
    I installed the latest service pack (SP3a) for SQL Server 2000 with no change in behavior.
    All of this leads me to believe that something is wrong with SQL Server. Has anyone else run into this problem? Any ideas?

    I am not overly familiar with the SQL Server network architecture, but there are scenarios that could explain your intermittent failures.
    When you connect to a database one of two things can happen, you can start your own process on the server that acts as communication to from the server locally, or you are put in a queue for a static (shared) process that does the same thing.
    Assuming that most databases are initially setup with singular processes per connection, and you have established a connection then you disconnect from the database you do not automatically or instantly kill your process running on the server. There are two primary reasons for this as far as I know. First, the database puts more priority on doing something then doing nothing. Cleaning up and removing your process would be considered doing nothing, accepting incoming connections would be considered doing something. Second, the process may have to stay around to ensure all commit or rollback is completed properly (not always true in every database).
    So, I would expect that there is a connection limit (perhaps between 50-80) that you are exceeding because you are firing these connections rapidly and even though you close the connection in your remote program, the database simply doesn't keep up. Most databases will "cleanup" reasonably quickly if they have the resources to do so, so if you were to put a 30 second delay between every connection it would probably work just fine. It would probably work fine if you put a 30 second delay between after every 20 connections too. It's a bit of balancing act.
    There would be a couple of ways to alleviate this constraint. Putting in delays can demonstrate that this is in fact a work load problem (constrained by total count of connections), but doesn't really help in production instances. You can change the maximum number of connections allowed by the database, however this threshold may be caused by hardware resource (memory) limitations as much as it is a parameter in the database. You may have to add memory to accommodate this many connections. You may have to constrain how much memory each connection gets (again controlled by database parameters). You may have to accept this as a resource constraint and write your code accordingly. This often manifests itself by taking advantage of transaction managers (or transaction manager logic) that will queue up requests until database resources are available.
    Again, I'm not a SQL Server expert, but I'm reasonably certain that most of what I said applies if not specifically at least generally.
    Good Luck.

  • Problem of loading the MS SQL Server 2000 driver for JDBC

    Thanks for your reply.
    I have already tried to give the full class path of .jar files to the System and User Variables but received the same error. I am doing BCA and developing my very first Project on Java.
    Please, tell me one thing. When I had installed MS SQL Server 2000 at my system first time then the 3 JAR files were present in the lib folder and all my codings of connectivity were working properly. Then due to some reasons, I had to format C drive and installed the MS SQL Server 2000 again then in the lib folder the 3 JAR files were not there. How it has happened? Then, I installed the downloaded driver of MS SQL Server 2000 for JDBC 1.4 then the JAR files were installed in the related downloaded driver folder. I manually copied them to the lib folder of MS SQL Server and gave that path to the Classpath of System and User Variables, but it didn't work.
    I am not understanding the reason that The Software which worked previously is not working correctly in second time of installing.
    I am using command line to develop my stand-alone project. Please help me.

    Don't bother with the System CLASSPATH, more often than not, it is not even used.
    When running from an IDE, set the project's library preferences.
    When running from a web container/application server configure the applications libraries in the server/container, see it's documentation.
    When running an applet, configure the [ codebase and/or archive |http://java.sun.com/docs/books/tutorial/deployment/applet/html.html] tags properly.
    When running from the command line with the [ "-cp" |http://java.sun.com/javase/6/docs/technotes/tools/solaris/java.html] option, the System CLASSPATH is ignored.
    When running from the command line with the "-jar" option, both the System CLASSPATH path and the "-cp" option are ignored, configure the [manifest file|http://java.sun.com/docs/books/tutorial/deployment/jar/downman.html] properly.
    When running any other way, the System CLASSPATH might be used.

  • Problem of loading the MS SQL Server 2000 Driver for JDBC 1.4.1

    Thanks for your reply.
    I have already tried to give the full class path of .jar files to the System and User Variables but received the same error. I am doing BCA and developing my very first Project on Java.
    Please, tell me one thing. When I had installed MS SQL Server 2000 at my system first time then the 3 JAR files were present in the lib folder and all my codings of connectivity were working properly. Then due to some reasons, I had to format C drive and installed the MS SQL Server 2000 again then in the lib folder the 3 JAR files were not there. How it has happened? Then, I installed the downloaded driver of MS SQL Server 2000 for JDBC 1.4 then the JAR files were installed in the related downloaded driver folder. I manually copied them to the lib folder of MS SQL Server and gave that path to the Classpath of System and User Variables, but it didn't work.
    I am not understanding the reason that The Software which worked previously is not working correctly in second time of installing.
    I am using command line to develop my stand-alone project. Please help me.

    Don't bother with the System CLASSPATH, more often than not, it is not even used.
    When running from an IDE, set the project's library preferences.
    When running from a web container/application server configure the applications libraries in the server/container, see it's documentation.
    When running an applet, configure the [ codebase and/or archive |http://java.sun.com/docs/books/tutorial/deployment/applet/html.html] tags properly.
    When running from the command line with the [ "-cp" |http://java.sun.com/javase/6/docs/technotes/tools/solaris/java.html] option, the System CLASSPATH is ignored.
    When running from the command line with the "-jar" option, both the System CLASSPATH path and the "-cp" option are ignored, configure the [manifest file|http://java.sun.com/docs/books/tutorial/deployment/jar/downman.html] properly.
    When running any other way, the System CLASSPATH might be used.

  • SQL Server 2000 Driver for JDBC

    I am trying to learn how to connect to SQL Server 2000 and I keep getting errors. I have set my classpath and read through the online books, but I can't fix it. I'm not sure if I'm missing something in the configuration, or at the database level. Here are the errors I'm getting followed by my code: By the way, is there a limit on how long the classpath can be?
    C:\j2sdkP>java TableMaker
    Exception in thread "main" java.lang.NoClassDefFoundError: com/microsoft/jdbc/ba
    se/BaseDriver
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:509)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
    3)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:246)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:54)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:193)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:265)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:262)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:322)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:130)
    at TableMaker.registerDriver(TableMaker.java:34)
    at TableMaker.<init>(TableMaker.java:22)
    at TableMaker.main(TableMaker.java:77)
    import java.sql.*;
    import sun.jdbc.odbc.JdbcOdbcDriver;
    public class TableMaker
    static String jdbcDriver = "com.microsoft.jdbc.sqlserver.SQLServerDriver";
    static String dbName = "Contacts";
    static String SQLCreate =
         "Create Table Contact_Info (" +
         "Contact_ID     Integer          Not null     Primary Key, " +
         "First_Name     Varchar(20)     Not null," +
         "MI          Char(1)          Null," +
         "Last_Name     Varchar(30)     Not null," +
         "Street          varchar(50)     Not null," +
         "City          varchar(30)     Not null," +
         "State          Char(2)          Not null," +
         "Zip          varchar(10)     Not null," +
    public TableMaker()
    registerDriver();
    public void setDatabaseName( String dbName )
    this.dbName=dbName;
    public void registerDriver()
    try {
    Class.forName( jdbcDriver );
    catch ( ClassNotFoundException e ){
    System.err.println(e.getMessage());
    public void execute( String SQLCommand )
    Connection con = null;
    Statement stmt = null;
    try {
    con = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:1433","test","test"); // test is both login and password
    stmt = con.createStatement();
    stmt.execute(SQLCommand);
    con.close();
    catch(Exception e) {
    System.err.println(e.getMessage());
    finally {
    try {
    if (con != null)
         con.close();
         if (stmt != null)
         stmt.close();
    catch (Exception ex) { }
    public static void main(String[] args)
    TableMaker tableMaker = new TableMaker();
    tableMaker.execute(SQLCreate);
    }

    Finally, I fix the problem! Can't put white space after ";" for CLASSPATH!!! for instance classpath=.; c:\..\*.jar doesn't work! it must be classpath=.;c:\..\*.jar The stupid JAVA!!! Thanks a lot.
    I have another problem, right now I can connect to SQL Server 2000 from standalone program, but I can't connect to my DB from servlet.
    ie. the following codes works for standalone program. but it doesn't work for servlet. Any help will be appreciated!
    // Make sure the JdbcOdbcDriver class is loaded
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    // Try to connect to a database via ODBC
    conn = DriverManager.getConnection(
    "jdbc:microsoft:sqlserver://127.0.01:1433", "sa","");

  • SQL Server 2000 Driver for JDBC SP3 and J2SE 5.0?

    Hi.
    On http://www.microsoft.com/downloads/details.aspx?FamilyID=07287b11-0502-461a-b138-2aa54bfdc03a&DisplayLang=en
    it says JDK versions up to 1.4 are supported (I guess that probably means NO), but I'm wondering if anyone knows if it's possible to use 1.5?
    Thanks!

    Hi.
    On
    http://www.microsoft.com/downloads/details.aspx?Family
    ID=07287b11-0502-461a-b138-2aa54bfdc03a&DisplayLang=en
    it says JDK versions up to 1.4 are supported (I guess
    that probably means NO), but I'm wondering if anyone
    knows if it's possible to use 1.5?
    Thanks!I can't imagine why not. They most likely have that list so that they can say we don't support 1.1.4 or something.
    But I gotta be perfectly honest with you. That driver (from the messages posted here) seems to be a real piece of rubbish. Gee I wonder why that would be? I recommend (based on my personal usage experience) the jtds driver http://jtds.sourceforge.net/ Which is free, open source and also a type 4 driver.

  • MS sql server 7 driver for JDBC

    Hi everyone,
    Where can I download the sql server 7 driver for JDBC. I searched on microsoft web site, and only saw the JDBC driver for sql server 2000. Also, what is the Class.forname() and URL will look like? Thanks.
    Houmin

    com.microsoft.jdbc.sqlserver.SQLServerDriver
    bye
    paolo

  • Problem in SQL Server 2000 Driver for Java Database Connectivity

    Hi,
    I have problem with MS SQL 2000 JDBC driver. I am using Type-4 driver for my application. I can able to connect through DSN. If I use Type-4 Driver to connect database means it gives the following exception.
    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.base.BaseExceptions.getException(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
         at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
         at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
         at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
         at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
         at java.sql.DriverManager.getConnection(Unknown Source)
         at java.sql.DriverManager.getConnection(Unknown Source)
         at test.TestDB.main(TestDB.java:17)
    My Java Code :
    String driver = "com.microsoft.jdbc.sqlserver.SQLServerDriver";
    Class.forName(driver);
    Connection con = DriverManager.getConnection("jdbc:microsoft:sqlserver://192.168.48.90:1433;User=sa;Password=sa;DatabaseName=GWCANADA");
    Statement st = con.createStatement();
    ResultSet rs = st.executeQuery("select * from emp");Do we have any other jdbc driver to connect MS SQL 2000 aprt from the Microsoft JDBC driver.
    Plese help me to resolve this problem
    Thanks
    ---Suresh

    Same problem is here: http://forum.java.sun.com/thread.jspa?threadID=419214&tstart=135
    Check that your server is running (telnet <hostname> 1433)
    --Xapp                                                                                                                                                                                                                                                                                                                   

  • Lack of TCP keepalive parameter in Microsoft SQL Server ODBC Driver for Linux

    Hello,
    the problem in the
    aforementioned driver is the lack of TCP keepalive parameter that results in hanged threads because of closed connections on the SQL Server side, but not closed
    sockets on the client side. This could happen due to network-related problems.
    The driver is used in mission critical 24/7 uptime application and due to hanged threads the application cannot continue it's work and it needs to be restarted.
    This is observed in the latest version of the driver on RHEL 5.6.
    If you need clarification please ask.
    Does anybody know any workaround to this situation or a solution that I'm not aware of?
    Thank you for your help,
    luk.s

    Find the TCP socket of the ODBC connection in your process and set the keep-alive option and keep-alive timeout on it.
    You can do that by interposing socket system call.
    Or use libkeepalive: http://www.tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/#libkeepalive

  • JDBC for Microsoft SQL Server 2000

    Hello,
    I have installed Microsoft SQL Server 2000 to establish a connection with JDK 1.4.1 and run the following code:
    import java.sql.Connection.*;
    import java.sql.*;
    public class Connect
    private java.sql.Connection con = null;
    private final String url = "jdbc:microsoft:sqlserver://";
    private final String serverName= "localhost";
    private final String portNumber = "1433";
    private final String databaseName= "cbi";
    private final String userName = "sa";
    private final String password = "";
    // Informs the driver to use server a side-cursor,
    // which permits more than one active statement
    // on a connection.
    private final String selectMethod = "cursor";
    // Constructor
    public Connect(){}
    private String getConnectionUrl()
    return url+serverName+":"+portNumber+";databaseName="+databaseName+";selectMethod="+selectMethod+";";
    private java.sql.Connection getConnection()
    try
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    con = java.sql.DriverManager.getConnection(getConnectionUrl(),userName,password);
    if(con!=null)
    System.out.println("Connection Successful!");
    catch(Exception e)
    e.printStackTrace();
    System.out.println("Error Trace in getConnection() : " + e.getMessage());
    return con;
    Display the driver properties, database details
    public void displayDbProperties()
    java.sql.DatabaseMetaData dm = null;
    java.sql.ResultSet rs = null;
    try
    con= this.getConnection();
    if(con!=null)
    dm = con.getMetaData();
    System.out.println("Driver Information");
    System.out.println("\tDriver Name: "+ dm.getDriverName());
    System.out.println("\tDriver Version: "+ dm.getDriverVersion ());
    System.out.println("\nDatabase Information ");
    System.out.println("\tDatabase Name: "+ dm.getDatabaseProductName());
    System.out.println("\tDatabase Version: "+ dm.getDatabaseProductVersion());
    System.out.println("Avalilable Catalogs ");
    rs = dm.getCatalogs();
    while(rs.next())
    System.out.println("\tcatalog: "+ rs.getString(1));
    rs.close();
    rs = null;
    closeConnection();
    else
    System.out.println("Error: No active Connection");
    catch(Exception e)
    e.printStackTrace();
    dm=null;
    private void closeConnection()
    try
    if(con!=null)
    con.close();
    con=null;
    catch(Exception e)
    e.printStackTrace();
    public static void main(String[] args) throws Exception
    Connect myDbTest = new Connect();
    myDbTest.displayDbProperties();
    but, I received the error that ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver, No active Connection.
    I added the 3 .jar files msbase.jar,mssqlserver.jar and msutil.jar to the System variables but it is not working. Is there any syntax for adding these .jar files to the System Variables?
    Please, help me and give me the solution for establishing the connection and loading the driver class. If I am doing anything wrong then please, tell me the right step.
    I am developing a project on Java and I have very little time left to accomplish it. Please help me.
    Thankyou.

    I had already given the .jar files to the User variables and System Variables but the driver class is still not loading. I had simply given the .jar file name for instance, msbase.jar;mssqlserver.jar;msutil.jar and also tried the path of .jar files i.e., C:\Microsoft SQL Server\-----------\lib\msbase.jar;C:\-------------lib\mssqlserver.jar;C:\----------------\lib\msutil.jar; but, both ways are not working. When I installed the MS SQL Server 2000 then in the lib folder, the 3 JAR files were not installed then, I downloaded a driver for MS SQL Server 2000 Driver for JDBC sp2, then, the JAR files were installed. Then, I copied those files to the lib folder of MS SQL Server and gave that path to the User and System Variables but it didn't work then I gave the original path of files where they are installed i.e., of the Driver's path which I downloaded from Microsoft but still now, my problem is not solved. Please help me.

Maybe you are looking for

  • How do I convert PDF to word on a mac?

    Hi, I'm new to apple products and i'm struggling to find how i convert a pdf file to word.  On a PC the option automatically popped up on the file or edit and right click.  There is no right click on a mac from what I can see and there is no option i

  • Results and a Procedure for SSD Upgrade on T410s

    After finding that my T410s 1.8" hard drive was 35% - 60% slower than the variety of 2.5" SATA Hard Drives in my older Thinkpads, I selected a Kingston SSDNow V+180 128GB for $219 for the SSD upgrade from Amazon because this Kingston model had the be

  • Zfs does not reclaim space after database table dropped

    Our Oracle DBA dropped 200GB of tables and zfs has not reclaimed the space. I have made sure we did not have any snapshots. When I do a du -h on the filesystem, it shows the correct space, but zfs list does not show the extra space. Any ideas?

  • Scaling text and shape made in lower res file?

    I created a selection, filled it and put text on top of it in a 72 ppi file and copied the group to an image with much higher resolution. I transformed the shape and text to make it bigger. Does doing this affect quality? It looked ok, I'm just curio

  • Files not deleting on Western Digital My Book Mac

    Hello, I recently deleted some time machine backups on my western digital my book mac. Unfortunately these files was not been deleted from the drive (the remaining disk space has not gone up circa 300GB). I have looked online and the issues seems to