Communications link failure #0

We are intermittently getting this error on our SQL server. The front end is
access and this happens every so often causing the users to have to exit out
of access and reconnect. I'm by no means a SQL expert, and our programmer
who manages this database isn't sure what it is either, he says it's like
the server is just "forgetting his password" and dumping the ODBC
connection...
Any ideas/help would be appreciated.
Thanks!
ScottHi
You don't give what version of MDAC or SQL Server that you are using!
http://www.aspfaq.com/show.asp?id=2160
http://msdn.microsoft.com/data/mdac/default.aspx
Searching Google for "Communications link failure" turns up quite a few
things, it seemed to be quite common with SQL Server 6.5!
You may want to check that you don't have connection pooling.
Try logging the ODBC commands (on the client) and using Profiler on the
server to pin point if there is one particular set of circumstances when it
occurs.
Check your SQL Server logs and Event logs (on client and server) to see if
there in any information or event that corresponds to the timing of your
disconnections.
Use the MDAC component check to show the version and if you have a
consistent installation.
HTH
John
"Scott McDonald" wrote:

> We are intermittently getting this error on our SQL server. The front end
is
> access and this happens every so often causing the users to have to exit o
ut
> of access and reconnect. I'm by no means a SQL expert, and our programmer
> who manages this database isn't sure what it is either, he says it's like
> the server is just "forgetting his password" and dumping the ODBC
> connection...
> Any ideas/help would be appreciated.
> Thanks!
> Scott
>
>|||it's SQL 2000 on Windows 2003 and using Access 2003 - sorry . MDAC is
newest, which I think is x.7 or something...
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:2B4BF663-A19B-4E40-B44A-D9684B757E4B@.microsoft.com...[vbcol=seagreen]
> Hi
> You don't give what version of MDAC or SQL Server that you are using!
> http://www.aspfaq.com/show.asp?id=2160
> http://msdn.microsoft.com/data/mdac/default.aspx
> Searching Google for "Communications link failure" turns up quite a few
> things, it seemed to be quite common with SQL Server 6.5!
> You may want to check that you don't have connection pooling.
> Try logging the ODBC commands (on the client) and using Profiler on the
> server to pin point if there is one particular set of circumstances when
> it
> occurs.
> Check your SQL Server logs and Event logs (on client and server) to see if
> there in any information or event that corresponds to the timing of your
> disconnections.
> Use the MDAC component check to show the version and if you have a
> consistent installation.
> HTH
> John
>
> "Scott McDonald" wrote:
>|||Hi
You may also want to switch protocols and check out the network in
general for possible problems.
John
Scott McDonald wrote:
> it's SQL 2000 on Windows 2003 and using Access 2003 - sorry . MDAC is
[vbcol=seagreen]
> newest, which I think is x.7 or something...
>
> "John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
> news:2B4BF663-A19B-4E40-B44A-D9684B757E4B@.microsoft.com...
using![vbcol=seagreen]
few[vbcol=seagreen]
the[vbcol=seagreen]
when[vbcol=seagreen]
see if[vbcol=seagreen]
your[vbcol=seagreen]
front end[vbcol=seagreen]
to exit[vbcol=seagreen]
programmer[vbcol=seagreen]
it's like[vbcol=seagreen]