ODBC Failed [Microsoft][ODBC SQL ...NamedPipes]ConnectionWrite (WrapperWrite()).

I am getting the following intermittant error upon accessing data
from
my server:

Run Time Error '3146' ODBC Failed [Microsoft][ODBC SQL Server
Driver]
[NamedPipes]ConnectionWrite (WrapperWrite()). (#59) [Microsoft][ODBC
SQL Server Driver][NamedPipes]General Network Error. Check your
documentation. (#11)


This is on a Windows XP computer running Access 2000. I have a query
that access my SQL Server database initiated by a Timer event every
minuite.


The server is Windows Server 2003 standard edition release 2 running
SQL Server 2000 service pack 4.


We have a very similar problem occuring on another computer with a
different application running. It ran fine when it was running on
Windows 2000, but began to have intermittant connection problems when
we converted the machine to XP.


Any ideas would be greatly appreciated!
Lisa

Re: ODBC Failed [Microsoft][ODBC SQL ...NamedPipes]ConnectionWrite (WrapperWrite()).

Lisa (lbach@sierrapine.com) writes:
> I am getting the following intermittant error upon accessing data from
> my server:
>
> Run Time Error '3146' ODBC Failed [Microsoft][ODBC SQL Server
> Driver]
> [NamedPipes]ConnectionWrite (WrapperWrite()). (#59) [Microsoft][ODBC
> SQL Server Driver][NamedPipes]General Network Error. Check your
> documentation. (#11)
>
>
> This is on a Windows XP computer running Access 2000. I have a query
> that access my SQL Server database initiated by a Timer event every
> minuite.
>
>
> The server is Windows Server 2003 standard edition release 2 running
> SQL Server 2000 service pack 4.
>
>
> We have a very similar problem occuring on another computer with a
> different application running. It ran fine when it was running on
> Windows 2000, but began to have intermittant connection problems when
> we converted the machine to XP.

The most likely reason is a disruption in the network, possibly involving
firewalls.

You could check in the SQL Server errorlog to see if there are any
stack dumps that can be correlated with these disconnections. In such
case it could be a bug in SQL Server. But network problems are far more
likely.

Any particular reason that you use named pipes rather than TCP/IP?


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downlo ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books .mspx