[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] General Network Error - (I have included the event log dump.)

I have a MS MSDE 2000 database that is serving 3 database clients. Intermittently, randomly, and more important daily, my clients receive a "SQL Database Connection Error", and they are kicked out of the database. This appears to be correlated when they are writing/retrieving a record.

MS MSDE then writes the following error in it's event log.

----------
Source: SORules.Gateway.LogErrors
Process ID: 2328

Database connection lost
Error #-2147467259
[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
(Source: Microsoft OLE DB Provider for SQL Server)
(SQL State: 08S01)
(NativeError: 11)
No Help file available

OpenRsRead
System.Runtime.InteropServices.COMException (0x80004005): [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
at ADODB.RecordsetClass.Open(Object Source, Object ActiveConnection, CursorTypeEnum CursorType, LockTypeEnum LockType, Int32 Options)
at SORules.Gateway.OpenRsRead(Command& C, Boolean& ForwardOnlyCursor)
Stack trace:
at ADODB.RecordsetClass.Open(Object Source, Object ActiveConnection, CursorTypeEnum CursorType, LockTypeEnum LockType, Int32 Options)
at SORules.Gateway.OpenRsRead(Command& C, Boolean& ForwardOnlyCursor)
----------

Any help, suggestions, or thoughts would be greatly appreciated. This is for a small business line of business application that is critical for everyday business operations. These problems have resulted in lost work, short tempers, and a just frank frustration.

I am just getting started with MS SQL technologies and really need some quality help.

Thank you for your time, and have a great day.

Cheers,
MarkBasically this means that there is a "connection problem" between the client and server parts of the SQL Server software. The error isn't specific because there are way too many places for these kinds of problems to hide, most of which can't be found by the machine that notices the problem.

If the people are having regular network problems (slowness, problems reaching specific machines in their networks, web browsing issues, etc), then fixing those problems should also fix the SQL problem.

If they aren't having regular network problems, then you have to play a bit of Sherlock Holmes to track down the culprit. If I were in this situation, I'd check:

1. Visit the Windows Update site from each machine using SQL. Be sure to get the latest windows and driver patches.
2. Ping the database server from each machine, investigate any significant differences in ping times.
3. Check the Network Interface Card in each machine (including the server)
4. Check the network hardware (routers, etc)
5. Come back here if that doesn't help.

-PatP