[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,
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:

[ODBC SQL Server Driver]Communication link failure

This error is being generated from a SQLServer2000 database being accessed
via ASP over the web, any suggestions for fixing it?
THANKS
--
John9 times out of 10 this is a NIC/Hub/Switch issue...can you have the network
guys stress test the connection (or are you the network guy?)
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"JohnB" <JohnB@.discussions.microsoft.com> wrote in message
news:185061E8-C62F-4E79-94EC-699844BE67D2@.microsoft.com...
> This error is being generated from a SQLServer2000 database being accessed
> via ASP over the web, any suggestions for fixing it?
> THANKS
> --
> John

[ODBC SQL Server Driver]Communication link failure

This error is being generated from a SQLServer2000 database being accessed
via ASP over the web, any suggestions for fixing it?
THANKS
John
9 times out of 10 this is a NIC/Hub/Switch issue...can you have the network
guys stress test the connection (or are you the network guy?)
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"JohnB" <JohnB@.discussions.microsoft.com> wrote in message
news:185061E8-C62F-4E79-94EC-699844BE67D2@.microsoft.com...
> This error is being generated from a SQLServer2000 database being accessed
> via ASP over the web, any suggestions for fixing it?
> THANKS
> --
> John

[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:
>

[Help]SQLServer Logon Failure ....

Hi!
I have a SQL server which version is SQL Server 8.0 and I want to change
this server's windows logon password. But, when I did then restart sql
service, I get this error message :"SQL Server Logon Failure". Is there any
way to change this password?
Registration properties : Windows authentication
Authentication mode : SQL Server and Windows
Best Regards,
AresChange the service login info - check
http://www.techgroup21.com/subpage.asp?subnavID=114.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"ares" <aresATasia-minor.info> wrote in message
news:uRCSkJkxEHA.2580@.TK2MSFTNGP10.phx.gbl...
> Hi!
> I have a SQL server which version is SQL Server 8.0 and I want to change
> this server's windows logon password. But, when I did then restart sql
> service, I get this error message :"SQL Server Logon Failure". Is there
any
> way to change this password?
> Registration properties : Windows authentication
> Authentication mode : SQL Server and Windows
> Best Regards,
> Ares
>
>|||Thanks for your help.
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:OiePlJmxEHA.1300@.TK2MSFTNGP14.phx.gbl...
> Change the service login info - check
> http://www.techgroup21.com/subpage.asp?subnavID=114.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "ares" <aresATasia-minor.info> wrote in message
> news:uRCSkJkxEHA.2580@.TK2MSFTNGP10.phx.gbl...
> any
>