DTS Gurus !


We have a SQL 2000 package which uses a data driven query
which makes use of two stored procedures.
GETNeededRecords() and ProcessNeededRecords() with
transformations defined. Each record in the
result set returned by the GETNeededRecords is used by the
ProcessNeededRecords(). The Data Driven
step has a log file which logs the error messages.
Consistently the package fails reporting error
the below listed error. There is not enough we could find
online. Any help in this regard is
appreciated.


Command Error in Data Driven Query:

Error Source: Microsoft OLE DB Provider for SQL Server
Error Description:[DBNETLIB][ConnectionRead (recv()).]
General network error. Check your network documentation.
Error Help File:
Error Help Context ID:0



If the package is running on the same server, I dont
understand why there should be network error.

The error say to me that it cannot open one of the DTS connections.
Basically it cannot see the server.

You say the package is running on the server, but does this mean you are sat
at the server logged onto the local console? If so just open and close each
connection in the package to validate them.

Running a package from Enterprise manager on a desktop is not running the
package on the server, but locally on your PC.

--
Darren Green
http://www.sqldts.com




"kk" <anonymous (AT) discussions (DOT) microsoft.com> wrote

The error also happen when we remote into that server box
and run the package using the enterprise manager on the
server. Why would the conection be lost when the packages
are run in the same box.

If we open and close connection for every step, wouldn't
it be a lot of running time for the package as our
packages run for hours.

Why would the package throw a network error when there is
no network involved.

Also we applied a MS patch for Win 2003 which seemed to
fix the problem 90% of the time, however we keep bumping
into it all the time. Also there is another Win 2003 box
where it seems to be running fine. What are we mising ?

Any help in this regard is appreciated.

I was looking here because, since we started using Windows
2003/MDAC 2.8, I have been seeing "General Network Errors"
from "Named Pipes" all over the place.

Since SQL Server is Client/Server it "always" uses a
network. In the log you will see "SQL Server is listening
on" and a list of networks. Cliconfg.exe can be used to
force using tcp/ip and the "Loop Back Adapter" for
connections on the local computer.

To me it looks like "Data Driven Queries" ignore the
Cliconfg settings and always use "Named Pipes" when
running locally (like thru SQLAgent).

The only solution I have found is to update the clients
that show this error to MDAC 2.8 and then substitute
the "Named Pipe DLL" dbnmpntw.dll (09-17-2003
2000.85.1022.42) that come
with "http://support.microsoft.com/default.aspx?scid=kb;en-
us;827452&Product=sql2k"


network error
From: "kk" <anonymous (AT) discussions (DOT) microsoft.com> Sent:
7/19/2004 12:24:47 PM




The error also happen when we remote into that server box
and run the package using the enterprise manager on the
server. Why would the conection be lost when the packages
are run in the same box.

If we open and close connection for every step, wouldn't
it be a lot of running time for the package as our
packages run for hours.

Why would the package throw a network error when there is
no network involved.

Also we applied a MS patch for Win 2003 which seemed to
fix the problem 90% of the time, however we keep bumping
into it all the time. Also there is another Win 2003 box
where it seems to be running fine. What are we mising ?

Any help in this regard is appreciated.