General network Error

Dominic Hébert

unread,

Jan 19, 2004, 3:54:39 PM1/19/04

to

I have some Jobs in the sceduler with the same problem.

The error is General network Error

The Client and the SErveur are the same, Only database or
table change.

I can have the error at any time a day.
I can have this error with Sceduler or directly into DTS.
I use the protocole TCP-IP only.

SQL SERVEUR version :
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003
Microsoft Corporation
Enterprise Edition on
Window's version :Windows NT 5.0 (Build 2195: Service Pack
4)
The last version of MDAC : MDAC 2.7 SP1 REFRESH with
Component Checker 2.0 from Microsoft.

--------------------------------------------------------
------- E --- x --- e --- m --- p --- l --- e ----------
--------------------------------------------------------
TSRun OnStart: DTSStep_DTSExecuteSQLTask_12

DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_22

DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_12

DTSRun OnStart: DTSStep_DTSDataPumpTask_15

DTSRun OnError: DTSStep_DTSDataPumpTask_15, Error = -
2147467259 (80004005)

Error string: [DBNETLIB][ConnectionWrite (send()).]
General network error. Check your network documentation.

Error source: Microsoft OLE DB Provider for SQL Server

Help file:

Help context: 0

Error Detail Records:

Error: -2147467259 (80004005); Provider Error: 11 (B)

Error string: [DBNETLIB][ConnectionWrite (send()).]
General network error. Check your network documentation.

Error source: Microsoft OLE DB Provider for SQL Server

Help file:

Help context: 0

DTSRun OnFinish: DTSStep_DTSDataPumpTask_15

DTSRun: Package execution complete.
--------------------------------------------------------

Thanks for your help.

Kevin McDonnell [MSFT]

unread,

Jan 19, 2004, 4:53:57 PM1/19/04

to

Did you see any corresponding problems with your network card in the NT
System Even log?
Does the problem reproduce easily or is it only under stress?
Does the problem happen if you enable Named Pipes or create a Named Pipes
Alias on the machine?

Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.

Dominic Hébert

unread,

Jan 19, 2004, 5:09:32 PM1/19/04

to

I try severall test with the network card on this Server
and on another servers and the result are comparable.

In the past I have Named Pipes network librairy but for
few days, I dont get the General Network Error.

I can reproduce the problem but generaly with only 3 or 4
main jobs. ( ~8 DTS packages )

I have alias with TCP-IP but I have uncheck named Pipe
because I always got the error when this librairy is
checked.

ThankS,
Dominic Hébert

>.
>

Kevin McDonnell [MSFT]

unread,

Jan 19, 2004, 6:01:30 PM1/19/04

to

When connections are being made on the local server (as with local jobs
running on the server with SQL Agent) it really doesn't pay to FORCE the
connection to use TCP sockets, with a TCP alias. Since the connection is
local to the server, the SQL Server can utilize Shared memory or Local
pipes and never touch the network.

Dominic Hébert

unread,

Jan 20, 2004, 4:29:38 PM1/20/04

to

ok. I'll try tonight to run the job with Name Pipe
Activated. I give you a feelback tomorrow.

thanks

>.
>

Dominic Hébert

unread,

Jan 30, 2004, 11:04:18 AM1/30/04

to

Ok now after 10 days I can tell you I don't received
again the General NEtwork Error.

But now I got some type of lock like LCK_M_S, OLEDB,
CXPACKET...

How I can eliminate this Wait Type ?

>.
>