| Groups | Blog | Home |
sql server odbc : [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" 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,
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" [quoted text, click to view] <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. [quoted text, click to view] "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 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? >
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" [quoted text, click to view] <james_topa@reyrey.com> wrote:
>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 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? >> >>
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 [quoted text, click to view] "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: > > >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 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? > >> > >> >
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" [quoted text, click to view] <james_topa@reyrey.com> 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: >> >> >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 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? >> >> >> >> >> >>
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" [quoted text, click to view] <james_topa@reyrey.com> 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: >> >> >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 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? >> >> >> >> >> >>
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |