[DBNETLIB]ConnectionWrite (send()) error

I've searched trying to find help for "[Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionWrite (send())", but couldn't find any solutions
(and precious few leads). I think I've figured out the problem, and wanted
to post it in case anyone else was looking also.
My enabled protocols in the SQL Server Client Network Utility, Named Pipes
and TCP/IP, were set to where TCP/IP was first in the list. I changed it to
where Named Pipes was at the top of the list, and my query (from my
workstation to the server) now runs instead of getting the error message
shown above.
Does anyone have anything else to add to this that might further clairfy the
issue?
Thanks,
Mike
TCP protocol is failing to connect...is the SQL Server listening on that
protocol? Look in the current SQL Server ERRORLOG for a line similar to:
SQL Server listening on TCP, shared memory, named pipes
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"mikron2" <mikron2@.discussions.microsoft.com> wrote in message
news:BDB8E5F9-D615-41BE-B07A-4F71F4AD053F@.microsoft.com...
> I've searched trying to find help for "[Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionWrite (send())", but couldn't find any
> solutions
> (and precious few leads). I think I've figured out the problem, and
> wanted
> to post it in case anyone else was looking also.
> My enabled protocols in the SQL Server Client Network Utility, Named Pipes
> and TCP/IP, were set to where TCP/IP was first in the list. I changed it
> to
> where Named Pipes was at the top of the list, and my query (from my
> workstation to the server) now runs instead of getting the error message
> shown above.
> Does anyone have anything else to add to this that might further clairfy
> the
> issue?
> Thanks,
> Mike
|||Two lines:
SQL server listening on n.n.n.n: 14yy.
SQL server listening on x.x.x.x: 14yy.
Replaced the actual numbers with n's, x's and y's, of course.
Mike
|||Sorry, I missed a line:
SQL server listening on TCP, Shared Memory, Named Pipes.
It's after the other two lines I mentioned earlier.
Mike
|||At least we know that its trying to listen
From your client machine, assuming you have Query Analyzer, try to make a
new connection. In the servername box, instead of SERVERNAME use
tcp:SERVERNAME, 1433
if that fails, try:
tcp:x.x.x.x, 14yy (replace x with your external ip, and 14yy with the
correct port)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"mikron2" <mikron2@.discussions.microsoft.com> wrote in message
news:9D5AC8FF-7CF9-4BC0-9B12-13206F8CE225@.microsoft.com...
> Sorry, I missed a line:
> SQL server listening on TCP, Shared Memory, Named Pipes.
> It's after the other two lines I mentioned earlier.
> Mike
>

[DBNETLIB]ConnectionWrite (send()) error

I've searched trying to find help for "[Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionWrite (send())", but couldn't find any soluti
ons
(and precious few leads). I think I've figured out the problem, and wanted
to post it in case anyone else was looking also.
My enabled protocols in the SQL Server Client Network Utility, Named Pipes
and TCP/IP, were set to where TCP/IP was first in the list. I changed it to
where Named Pipes was at the top of the list, and my query (from my
workstation to the server) now runs instead of getting the error message
shown above.
Does anyone have anything else to add to this that might further clairfy the
issue?
Thanks,
MikeTCP protocol is failing to connect...is the SQL Server listening on that
protocol? Look in the current SQL Server ERRORLOG for a line similar to:
SQL Server listening on TCP, shared memory, named pipes
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"mikron2" <mikron2@.discussions.microsoft.com> wrote in message
news:BDB8E5F9-D615-41BE-B07A-4F71F4AD053F@.microsoft.com...
> I've searched trying to find help for "[Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionWrite (send())", but couldn't find any
> solutions
> (and precious few leads). I think I've figured out the problem, and
> wanted
> to post it in case anyone else was looking also.
> My enabled protocols in the SQL Server Client Network Utility, Named Pipes
> and TCP/IP, were set to where TCP/IP was first in the list. I changed it
> to
> where Named Pipes was at the top of the list, and my query (from my
> workstation to the server) now runs instead of getting the error message
> shown above.
> Does anyone have anything else to add to this that might further clairfy
> the
> issue?
> Thanks,
> Mike|||Two lines:
SQL server listening on n.n.n.n: 14yy.
SQL server listening on x.x.x.x: 14yy.
Replaced the actual numbers with n's, x's and y's, of course.
Mike|||Sorry, I missed a line:
SQL server listening on TCP, Shared Memory, Named Pipes.
It's after the other two lines I mentioned earlier.
Mike|||At least we know that its trying to listen
From your client machine, assuming you have Query Analyzer, try to make a
new connection. In the servername box, instead of SERVERNAME use
tcp:SERVERNAME, 1433
if that fails, try:
tcp:x.x.x.x, 14yy (replace x with your external ip, and 14yy with the
correct port)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"mikron2" <mikron2@.discussions.microsoft.com> wrote in message
news:9D5AC8FF-7CF9-4BC0-9B12-13206F8CE225@.microsoft.com...
> Sorry, I missed a line:
> SQL server listening on TCP, Shared Memory, Named Pipes.
> It's after the other two lines I mentioned earlier.
> Mike
>

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

[DBNETLIB][ConnectionWrite (send()).]General network error

SQL Server Spec
SQL 2000, 8.00.2187 SP4 standard edition
windows 2003 SP1
sqlserver driver 2000.86.1830.00
webserver
windows 2003 r2, standard edition service pack2
sqlserver driver 2000.86.3959.00
we received "intermittance"
Error Number -2147467259 (&H80004005)
[DBNETLIB][ConnectionWrite (send()).]General network error. Check yo
ur
network documentation.
We already do this as mention in microsoft website
on SynAttackProtect:
http://support.microsoft.com/defaul...kb;en-us;899599
Any idea or any one have experience on this?
Cheers,
Liang Yewsorry,
SQL Server
windows 2003 SP2
SQL 2000, 8.00.2187 SP4 standard edition
sqlserver driver 2000.86.3959.00
"soonyu" wrote:

> SQL Server Spec
> SQL 2000, 8.00.2187 SP4 standard edition
> windows 2003 SP1
> sqlserver driver 2000.86.1830.00
> webserver
> windows 2003 r2, standard edition service pack2
> sqlserver driver 2000.86.3959.00
> we received "intermittance"
> Error Number -2147467259 (&H80004005)
> [DBNETLIB][ConnectionWrite (send()).]General network error. Check
your
> network documentation.
> We already do this as mention in microsoft website
> on SynAttackProtect:
> http://support.microsoft.com/defaul...kb;en-us;899599
> Any idea or any one have experience on this?
> Cheers,
> Liang Yew

[DBNETLIB][ConnectionWrite (send()).]General network error

SQL Server Spec
SQL 2000, 8.00.2187 SP4 standard edition
windows 2003 SP1
sqlserver driver 2000.86.1830.00
webserver
windows 2003 r2, standard edition service pack2
sqlserver driver 2000.86.3959.00
we received "intermittance"
Error Number -2147467259 (&H80004005)
[DBNETLIB][ConnectionWrite (send()).]General network error. Check your
network documentation.
We already do this as mention in microsoft website
on SynAttackProtect:
http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
Any idea or any one have experience on this?
Cheers,
Liang Yew
sorry,
SQL Server
windows 2003 SP2
SQL 2000, 8.00.2187 SP4 standard edition
sqlserver driver 2000.86.3959.00
"soonyu" wrote:

> SQL Server Spec
> SQL 2000, 8.00.2187 SP4 standard edition
> windows 2003 SP1
> sqlserver driver 2000.86.1830.00
> webserver
> windows 2003 r2, standard edition service pack2
> sqlserver driver 2000.86.3959.00
> we received "intermittance"
> Error Number -2147467259 (&H80004005)
> [DBNETLIB][ConnectionWrite (send()).]General network error. Check your
> network documentation.
> We already do this as mention in microsoft website
> on SynAttackProtect:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> Any idea or any one have experience on this?
> Cheers,
> Liang Yew

[DBNETLIB][ConnectionWrite (send()).] General network error.

Hi,
in our environment
- Windows XP
- SQL Server Express 2005
- Internet connection via TCP/IP protocol

The described network error occurs, when we unplug the network cable:
[DBNETLIB][ConnectionWrite (send()).] General network error.

The affected database resides on the locally installed SQLExpress, it doesn't use any network connections. The error doesn't occur immediately, in most cases there are up to 30 seconds where data can be (correctly!) written to the recordset, but after that timeout the connetion is broken.

We already tried out the described workarounds:
- disable named pipes protocol
- set SynAttackProtect=0 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

The error doesn't occur with MSDE (SQL 2000) or under Vista.

Thanks for help!

Mathias

I suggest using shared memory to connect locally or making sure your server specification is one that correctly gets resolved to use the loopback (e.g. .\ or (local) or localhost). You may also want to see if your hosts file has an entry for the machine to make sure it resolves its own name. Right now, it appears as though your communications are going out over the network. You may have some amount of data transfer after unplugging the cable because the network connection is buffered, so the server still has that much data in its network buffer before it runs out. I think the connection timeout is consuming the bulk of that 30 seconds. Vista most likely has its own hostname in its hosts file, or has some other trick for self-resolving its computer name. More than likely, your instance of SQL 2000 is using shared memory to connect or using a different specification of the hostname.

Hope that helps,

John

[DBNETLIB][ConnectionWrite (send()).] errors

We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.

Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.

Does anyone have any ideas ?

Hi Brian,

I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.

The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...

I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp

Both to no avail....

Was wondering if you'd found a resolution yet?

Best regards

Keith
|||

For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.

HTH

|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue

[DBNETLIB][ConnectionWrite (send()).] errors

We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.

Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.

Does anyone have any ideas ?

Hi Brian,

I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.

The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...

I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp

Both to no avail....

Was wondering if you'd found a resolution yet?

Best regards

Keith
|||

For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.

HTH

|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue