Communication Link Failure

Hello everyone,
We have upgraded our database server from SQL Server
7.0/sp4 to SQL Server 2000/sp2. Since then the client
application accessing the database has consistent 08S01
errors with "Communication Link Failure" messages.
There is a pop up dialog box that provides instant
information as part of the application. Most of the time
those 08S01 problems start occurring when this window
pops up. By default, SQL Server 2000 set 'Query Timeout'
to 600. I have changed it to 0 (or unlimited) just to
avoid timing out of queries (just in case the query is
kept open in the dialog box). I found from users that the
errors have reduced (to some extent) but they are not
eliminated.
Has someone experienced such problems in the past? Your
comments and help is welcome.
Thanks in advance,
mzeeshanThe latest SQL2k Service Pack is 3a, start by applying this. It could be a
problem on the client rather than the server, ensure the clients have the
current version of MDAC installed.
--
HTH
Ryan Waight, MCDBA, MCSE
"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
news:0f1301c38a83$0ac83e30$a401280a@.phx.gbl...
> Hello everyone,
> We have upgraded our database server from SQL Server
> 7.0/sp4 to SQL Server 2000/sp2. Since then the client
> application accessing the database has consistent 08S01
> errors with "Communication Link Failure" messages.
> There is a pop up dialog box that provides instant
> information as part of the application. Most of the time
> those 08S01 problems start occurring when this window
> pops up. By default, SQL Server 2000 set 'Query Timeout'
> to 600. I have changed it to 0 (or unlimited) just to
> avoid timing out of queries (just in case the query is
> kept open in the dialog box). I found from users that the
> errors have reduced (to some extent) but they are not
> eliminated.
> Has someone experienced such problems in the past? Your
> comments and help is welcome.
> Thanks in advance,
> mzeeshan

Communication Link Failure

Since we upgraded our server running SQL Server 2000 from Windows 2000 Server to Windows 2003 Server, our clients started getting the following error when we insert a new tape into the tape drive:
ODBC error:[Microsoft][ODBC SQL Server Driver]Communication link failure
Any ideas why inserting a tape would cause an error on client applications? (Happens daily)I have encountered the same ODBC error starting early Jan 04. It happens daily as well and is causing a lot of inconvenience to our clients.
Any ideas what will cause this type of communication link failure ?