[Microsoft][ODBC SQL Server Driver][Named Pipes] ConnectionWrite (WrapperWrite())

Hi,

I got the error message "[Microsoft][ODBC SQL Server Driver][Named Pipes] ConnectionWrite (WrapperWrite())" from my VB6 application that connects to SQL Server 2000.

How to fix this?

Can you post the full error. The posted message is too generic.
http://groups.google.com/groups/search?q=ConnectionWrite+%28WrapperWrite%28%29&qt_s=Search

[DBNETLIB][ConnetionWrite (WrapperWrite()).]General network error. Check your ne

Hi
While running a DTS, many times the error message: "[DBNETLIB][ConnetionWrite (WrapperWrite()).]General network error. Check your network documentation." appears.
Does somebody knows why?

I am running the DTS from a computer (not the server where the DTS is stored) and it is connected without any problem when this happens.

Thanks!!
Regards
Lautaro - Argentina.Do you get your results that your looking for from the dts?|||This looks like a network connectivity issue to me. Check (1) Network Connectivity by pinging, etc. (2) Check O/S security and permissions on any files you are trying to access, and (3) Check SQL Server login issues (i.e. SQL Service logins etc).

Great Detailed Error Messages Brought To Us By Microsoft ! ;)

Michael D.|||Hi

I am getting the same Wrapperwrite error .

The server is windows NT running SQL6.5 with all the latest service packs
The client machines are running all different operating systems.
The ODBC connections on the clients and server use either TCP/IP or named pipes but I get the same error on all clients.
The clients and server connect to a sql 6.5 database and when requesting information about certain clients, not all, the wrapperwrite error comes up and i have to close the progarm down.

I have heard people say on forums the it could be to do with the network but please note that this also happens on the server!

can any one help Please

Cheers|||General Network errors are commonly caused by tcp resets on the network.
You'll want to capture as much data about the clients and the statements they're executing using PROFILER.

Select All Errors and Warnings
RPC: Completed, Starting, sp Recompile
TSQL BatchCompleted, BatchStarting
Stmt:Starting

[DBNETLIB][ConnectionWrite(WrapperWrite()).]General network error. Check your network

I'm getting the following error on Windows XP clients only:
[DBNETLIB][ConnectionWrite(WrapperWrite()).]General network error. C
heck
your network documentation.
This error seems to occur at random times of inactivity on my application.
Here is how I am configured:
Windows 2000 Server - Standard
Windows 2000 and Windows XP Pro Clients
SQL Server 2000
MDAC 2.7 or 2.8 on various clients
The error does not occur on Windows 2000 clients, only on Windows XP Pro
clients.
My application first opens a connection to a server database. Every 2
minutes an application watchdog timer triggers and attempts to write an
timestamp value to a data table. After some period of time (seemingly
random) the attempted write fails and I get the above error message,
followed by a "Connection failure." error.
Can anyone point me in the right direction on how to fix this problem?
Thanks,
Al WillisHi Al,
I would try to capture the problem using both SQL Profiler on the
backend, and network traces on the client machines.
General Network errors are commonly caused by tcp resets on the network.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Most probably problem with NIC drivers or network harware on specific
computers.
Also it will much help if you do not expect an open connection to stay
connected forever and make new connection after for each triggering of your
watchdog.
Bojidar Alexandrov
"Al Willis" <alwillisj01@.sbcglobal.net> wrote in message
news:409aa583$1@.newsgroups.borland.com...
> I'm getting the following error on Windows XP clients only:
> [DBNETLIB][ConnectionWrite(WrapperWrite()).]General network error.
Check
> your network documentation.
> This error seems to occur at random times of inactivity on my application.
> Here is how I am configured:
> Windows 2000 Server - Standard
> Windows 2000 and Windows XP Pro Clients
> SQL Server 2000
> MDAC 2.7 or 2.8 on various clients
>
> Development Software
> --
> Delphi 6, update 2
> CoreLabs dbExpress driver for SQL Server
> The error does not occur on Windows 2000 clients, only on Windows XP Pro
> clients.
> My application first opens a connection to a server database. Every 2
> minutes an application watchdog timer triggers and attempts to write an
> timestamp value to a data table. After some period of time (seemingly
> random) the attempted write fails and I get the above error message,
> followed by a "Connection failure." error.
> Can anyone point me in the right direction on how to fix this problem?
> Thanks,
> Al Willis
> Enviroment
> --
> Windows 2000 Server - Standard
> Windows 2000 and Windows XP Pro Clients
> SQL Server 2000
> MDAC 2.7 or 2.8 on various clients
>
>|||Kevin,
Thanks for the reply.
I looked at the SQL Profiler. What categories should I trace to find my
problem?
Al Willis|||Hi Al,
You'll want to capture as much data about the clients and the
statements they're executing.
Select All Errors and Warnings
RPC: Completed, Starting, sp Recompile
TSQL BatchCompleted, BatchStarting
Stmt:Starting
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

[DBNETLIB][ConnectionWrite (WrapperWrite()).] General Network error. Check

Dear All,
I am getting this error frequently and some times sql server is getting
stopped automatically.
[DBNETLIB][ConnectionWrite (WrapperWrite()).] General Network error. Check
you network documentation.
Can any one help me out to get rid of this.
OS : Windows 2000 professional
SQL Server version is 2000
Thanks and Regards,
PeriHi Peri,
Here are some things I would do if I were in your shoes:
1) Check the Event Log for Network problems... Specif with the Network Card
2) If the SQL Server is in another subnet, check the router for errors
3) Check HOW you are connecting, use TCPIP if you can
4) Ping your machine so it pings over and over (see /flags help).. See if
you ever get dropped
5) Check for issues with the CLIENT machine to
That's all I can think of right now.. Good luck!
Erik
"Peri" <lperi@.CSPL.com> wrote in message
news:emmKD1CaFHA.3132@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I am getting this error frequently and some times sql server is getting
> stopped automatically.
> [DBNETLIB][ConnectionWrite (WrapperWrite()).] General Network error. Check
> you network documentation.
> Can any one help me out to get rid of this.
> OS : Windows 2000 professional
> SQL Server version is 2000
> Thanks and Regards,
> Peri
>|||I ran across this problem on my XP machine that went away when I re-loaded t
he machine and did NOT install Service Pack 2 of Windows. I still haven't f
igured out how to fix it yet. Maybe this information will lead you in the r
ight direction.