I have a third party Client (Rational Clearquest) connecting to a SQL server
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" after 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?
You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:
>I have a third party Client (Rational Clearquest) connecting to a SQL server
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" after 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?
|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:
> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>
|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:
> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>
|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
Showing posts with label connecting. Show all posts
Showing posts with label connecting. Show all posts
Thursday, March 8, 2012
[ODBC SQL Server Driver]Communication Link Failure
I have a third party Client (Rational Clearquest) connecting to a SQL server
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" aft
er 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:
>I have a third party Client (Rational Clearquest) connecting to a SQL serve
r
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" af
ter 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:
> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
>|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:
> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" aft
er 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:
>I have a third party Client (Rational Clearquest) connecting to a SQL serve
r
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" af
ter 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:
> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
>|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:
> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>
Tuesday, March 6, 2012
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
I'm using JBuilder X, writing a client application and connecting to
database
SQL Server 2000 with JDBC driver.
when i have Windows Xp Pro with service Pack 1
i don't have a problem
all works
now with Windows Xp Pro and service Pack 2 i have this problem
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
See com.borland.dx.dataset.DataSetException error code: BASE+66
com.borland.dx.dataset.DataSetException: [Microsoft][SQLServer 2000 Driver
for JDBC]Error establishing socket.
at com.borland.dx.dataset.DataSetException.a(Unknown Source)
at com.borland.dx.dataset.DataSetException.throwExcep tion(Unknown Source)
at com.borland.dx.dataset.DataSetException.SQLExcepti on(Unknown Source)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
Chained exception:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error
establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<in it>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnecti on.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplC onnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknow n Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:517)
at java.sql.DriverManager.getConnection(DriverManager .java:177)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
ava.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error
establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<in it>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnecti on.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplC onnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknow n Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:517)
at java.sql.DriverManager.getConnection(DriverManager .java:177)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
Thanks very much!
Take a look at the firewall configuration. XP SP2 comes with a firewall
that blocks all ports by default.
Alin,
The jTDS Project.
|||thanks .
the firewall want's one exeption for sql server
database
SQL Server 2000 with JDBC driver.
when i have Windows Xp Pro with service Pack 1
i don't have a problem
all works
now with Windows Xp Pro and service Pack 2 i have this problem
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
See com.borland.dx.dataset.DataSetException error code: BASE+66
com.borland.dx.dataset.DataSetException: [Microsoft][SQLServer 2000 Driver
for JDBC]Error establishing socket.
at com.borland.dx.dataset.DataSetException.a(Unknown Source)
at com.borland.dx.dataset.DataSetException.throwExcep tion(Unknown Source)
at com.borland.dx.dataset.DataSetException.SQLExcepti on(Unknown Source)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
Chained exception:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error
establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<in it>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnecti on.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplC onnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknow n Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:517)
at java.sql.DriverManager.getConnection(DriverManager .java:177)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
ava.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error
establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<in it>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnecti on.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplC onnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknow n Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:517)
at java.sql.DriverManager.getConnection(DriverManager .java:177)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
Thanks very much!
Take a look at the firewall configuration. XP SP2 comes with a firewall
that blocks all ports by default.
Alin,
The jTDS Project.
|||thanks .
the firewall want's one exeption for sql server
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for us
We changed from sql 7 to 2000, crissis mode.
One use with a laptop keeps getting the error when connecting to the sql
server.
SQL 2000 latest, mixed mode.
Laptop xp pro latest, mdac is latest.
I looked up sql server 26000 and 18452. I was not able to resolve the
problem. Still an untrusted connection.
I do know it is in the user profile but what?
Hi Brian,
Just to be sure, you have some machines working and one particular machine
(the laptop) is not working, right? Are you using Named Pipes or TCP-IP? Is
the laptop using a trusted connection or SQL Server security mode? What was
the exact text of the error message? What things have you tried that did not
resolve the problem?
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"BrianMultiLanguage" <BrianMultiLanguage@.discussions.microsoft.com> wrote in
message news:3D81F886-58B5-4C09-AA8A-1529B54CE72B@.microsoft.com...
> We changed from sql 7 to 2000, crissis mode.
> One use with a laptop keeps getting the error when connecting to the sql
> server.
> SQL 2000 latest, mixed mode.
> Laptop xp pro latest, mdac is latest.
> I looked up sql server 26000 and 18452. I was not able to resolve the
> problem. Still an untrusted connection.
> I do know it is in the user profile but what?
One use with a laptop keeps getting the error when connecting to the sql
server.
SQL 2000 latest, mixed mode.
Laptop xp pro latest, mdac is latest.
I looked up sql server 26000 and 18452. I was not able to resolve the
problem. Still an untrusted connection.
I do know it is in the user profile but what?
Hi Brian,
Just to be sure, you have some machines working and one particular machine
(the laptop) is not working, right? Are you using Named Pipes or TCP-IP? Is
the laptop using a trusted connection or SQL Server security mode? What was
the exact text of the error message? What things have you tried that did not
resolve the problem?
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"BrianMultiLanguage" <BrianMultiLanguage@.discussions.microsoft.com> wrote in
message news:3D81F886-58B5-4C09-AA8A-1529B54CE72B@.microsoft.com...
> We changed from sql 7 to 2000, crissis mode.
> One use with a laptop keeps getting the error when connecting to the sql
> server.
> SQL 2000 latest, mixed mode.
> Laptop xp pro latest, mdac is latest.
> I looked up sql server 26000 and 18452. I was not able to resolve the
> problem. Still an untrusted connection.
> I do know it is in the user profile but what?
Saturday, February 25, 2012
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).
We are randomly experiencing this error when connecting to SQL W2K from web
servers using ODBC. I see numerous links on the web but real answers.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).
Hi Brent,
I would make a network trace on the client and the server. I'll bet you
can't reproduce this if the client and server are on the same machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
servers using ODBC. I see numerous links on the web but real answers.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).
Hi Brent,
I would make a network trace on the client and the server. I'll bet you
can't reproduce this if the client and server are on the same machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).
We are randomly experiencing this error when connecting to SQL W2K from web
servers using ODBC. I see numerous links on the web but real answers.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (se
nd()).Hi Brent,
I would make a network trace on the client and the server. I'll bet you
can't reproduce this if the client and server are on the same machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
servers using ODBC. I see numerous links on the web but real answers.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (se
nd()).Hi Brent,
I would make a network trace on the client and the server. I'll bet you
can't reproduce this if the client and server are on the same machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Sunday, February 19, 2012
[DBNETLIB][ConnectionWrite (send()).] errors
We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.
Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.
Does anyone have any ideas ?
I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.
The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...
I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp
Both to no avail....
Was wondering if you'd found a resolution yet?
Best regards
Keith
|||
For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.
HTH
|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue
[DBNETLIB][ConnectionWrite (send()).] errors
We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.
Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.
Does anyone have any ideas ?
I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.
The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...
I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp
Both to no avail....
Was wondering if you'd found a resolution yet?
Best regards
Keith
|||
For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.
HTH
|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue
Subscribe to:
Posts (Atom)