Discussion:
ConnectionRead (recv()) error
(too old to reply)
Koen Vueghs
2003-07-04 09:43:43 UTC
Permalink
We get almost every day the following error:

Source = Microsoft OLE DB Provider for ODBC Drivers,
Description = [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionRead (recv()).

*) We are using Win2K SP3 and a seperate W2K Server with
SQL server
*) The error occurs on two different systems
*) MDAC 2.6 with latest SP
*) We are using TCP/IP as communication layer
*) Searches on the internet shows more people with this
problem but no answers are given
Val Mazur
2003-07-04 12:43:06 UTC
Permalink
Hi,

Did you try to use native OLEDB provider for SQL Server? Is it same problem?
Since you are working with SQL Server, using of OLEDB for ODBC is a
preferable way to work with the database

--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Source = Microsoft OLE DB Provider for ODBC Drivers,
Description = [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionRead (recv()).
*) We are using Win2K SP3 and a seperate W2K Server with
SQL server
*) The error occurs on two different systems
*) MDAC 2.6 with latest SP
*) We are using TCP/IP as communication layer
*) Searches on the internet shows more people with this
problem but no answers are given
koen vueghs
2003-07-04 13:18:44 UTC
Permalink
Thanks for the quick response. We are using MSDASQL as
provider and will change it to SQLOLEDB.

We hope that it helps. I'll post another reply next week
with the results.
-----Original Message-----
Hi,
Did you try to use native OLEDB provider for SQL Server?
Is it same problem?
Since you are working with SQL Server, using of OLEDB for
ODBC is a
preferable way to work with the database
--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Source = Microsoft OLE DB Provider for ODBC Drivers,
Description = [Microsoft][ODBC SQL Server Driver]
[DBNETLIB]
Post by Koen Vueghs
ConnectionRead (recv()).
*) We are using Win2K SP3 and a seperate W2K Server with
SQL server
*) The error occurs on two different systems
*) MDAC 2.6 with latest SP
*) We are using TCP/IP as communication layer
*) Searches on the internet shows more people with this
problem but no answers are given
.
Koen Vueghs
2003-07-10 06:30:09 UTC
Permalink
Hi,

As I said we changed to the native OLEDB provider for SQL
server but still have the ConnectionRead problem (but now
with extra text general network error check your
documentation

So wil still have the problem :(
-----Original Message-----
Hi,
Did you try to use native OLEDB provider for SQL Server?
Is it same problem?
Since you are working with SQL Server, using of OLEDB for
ODBC is a
preferable way to work with the database
--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Source = Microsoft OLE DB Provider for ODBC Drivers,
Description = [Microsoft][ODBC SQL Server Driver]
[DBNETLIB]
Post by Koen Vueghs
ConnectionRead (recv()).
*) We are using Win2K SP3 and a seperate W2K Server with
SQL server
*) The error occurs on two different systems
*) MDAC 2.6 with latest SP
*) We are using TCP/IP as communication layer
*) Searches on the internet shows more people with this
problem but no answers are given
.
Val Mazur
2003-07-10 12:51:32 UTC
Permalink
Hi,

What I have found so far is that error message maybe related to installation
of SQL Server with SP1. Since you are using SP3 it is probably something
*new*. What is your connection string? Could you post it here?

--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Hi,
As I said we changed to the native OLEDB provider for SQL
server but still have the ConnectionRead problem (but now
with extra text general network error check your
documentation
So wil still have the problem :(
-----Original Message-----
Hi,
Did you try to use native OLEDB provider for SQL Server?
Is it same problem?
Since you are working with SQL Server, using of OLEDB for
ODBC is a
preferable way to work with the database
--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Source = Microsoft OLE DB Provider for ODBC Drivers,
Description = [Microsoft][ODBC SQL Server Driver]
[DBNETLIB]
Post by Koen Vueghs
ConnectionRead (recv()).
*) We are using Win2K SP3 and a seperate W2K Server with
SQL server
*) The error occurs on two different systems
*) MDAC 2.6 with latest SP
*) We are using TCP/IP as communication layer
*) Searches on the internet shows more people with this
problem but no answers are given
.
Koen Vueghs
2003-07-12 20:52:37 UTC
Permalink
We were running Windows 2k Server with SP3 but did not
install any service pack for SQL server.
When we installed SP3 for SQL server it did not resolve
the problem. I can post the connectionstring monday when I
am back at work, but it is pretty standard....
-----Original Message-----
Hi,
What I have found so far is that error message maybe
related to installation
of SQL Server with SP1. Since you are using SP3 it is
probably something
*new*. What is your connection string? Could you post it
here?
--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Hi,
As I said we changed to the native OLEDB provider for
SQL
Post by Koen Vueghs
server but still have the ConnectionRead problem (but
now
Post by Koen Vueghs
with extra text general network error check your
documentation
So wil still have the problem :(
-----Original Message-----
Hi,
Did you try to use native OLEDB provider for SQL
Server?
Post by Koen Vueghs
Is it same problem?
Since you are working with SQL Server, using of OLEDB
for
Post by Koen Vueghs
ODBC is a
preferable way to work with the database
--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Source = Microsoft OLE DB Provider for ODBC Drivers,
Description = [Microsoft][ODBC SQL Server Driver]
[DBNETLIB]
Post by Koen Vueghs
ConnectionRead (recv()).
*) We are using Win2K SP3 and a seperate W2K Server
with
Post by Koen Vueghs
Post by Koen Vueghs
SQL server
*) The error occurs on two different systems
*) MDAC 2.6 with latest SP
*) We are using TCP/IP as communication layer
*) Searches on the internet shows more people with
this
Post by Koen Vueghs
Post by Koen Vueghs
problem but no answers are given
.
.
Koen Vueghs
2003-07-14 14:08:32 UTC
Permalink
Our connectionstring is now:

"Provider=SQLOLEDB; Data Source=PC12;Inital
Catalog=OASE;User id=xxxx;Password=xxxx"
-----Original Message-----
Hi,
What I have found so far is that error message maybe
related to installation
of SQL Server with SP1. Since you are using SP3 it is
probably something
*new*. What is your connection string? Could you post it
here?
--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Hi,
As I said we changed to the native OLEDB provider for
SQL
Post by Koen Vueghs
server but still have the ConnectionRead problem (but
now
Post by Koen Vueghs
with extra text general network error check your
documentation
So wil still have the problem :(
-----Original Message-----
Hi,
Did you try to use native OLEDB provider for SQL
Server?
Post by Koen Vueghs
Is it same problem?
Since you are working with SQL Server, using of OLEDB
for
Post by Koen Vueghs
ODBC is a
preferable way to work with the database
--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Source = Microsoft OLE DB Provider for ODBC Drivers,
Description = [Microsoft][ODBC SQL Server Driver]
[DBNETLIB]
Post by Koen Vueghs
ConnectionRead (recv()).
*) We are using Win2K SP3 and a seperate W2K Server
with
Post by Koen Vueghs
Post by Koen Vueghs
SQL server
*) The error occurs on two different systems
*) MDAC 2.6 with latest SP
*) We are using TCP/IP as communication layer
*) Searches on the internet shows more people with
this
Post by Koen Vueghs
Post by Koen Vueghs
problem but no answers are given
.
.
Koen Vueghs
2003-07-15 06:15:14 UTC
Permalink
Yep, it is driving me crazy.....
-----Original Message-----
Still same error?
--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
"Provider=SQLOLEDB; Data Source=PC12;Inital
Catalog=OASE;User id=xxxx;Password=xxxx"
-----Original Message-----
Hi,
What I have found so far is that error message maybe
related to installation
of SQL Server with SP1. Since you are using SP3 it is
probably something
*new*. What is your connection string? Could you post
it
Post by Koen Vueghs
here?
--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Hi,
As I said we changed to the native OLEDB provider for
SQL
Post by Koen Vueghs
server but still have the ConnectionRead problem (but
now
Post by Koen Vueghs
with extra text general network error check your
documentation
So wil still have the problem :(
-----Original Message-----
Hi,
Did you try to use native OLEDB provider for SQL
Server?
Post by Koen Vueghs
Is it same problem?
Since you are working with SQL Server, using of
OLEDB
Post by Koen Vueghs
for
Post by Koen Vueghs
ODBC is a
preferable way to work with the database
--
Val Mazur
Microsoft MVP
Post by Koen Vueghs
Source = Microsoft OLE DB Provider for ODBC
Drivers,
Post by Koen Vueghs
Post by Koen Vueghs
Post by Koen Vueghs
Description = [Microsoft][ODBC SQL Server Driver]
[DBNETLIB]
Post by Koen Vueghs
ConnectionRead (recv()).
*) We are using Win2K SP3 and a seperate W2K
Server
Post by Koen Vueghs
with
Post by Koen Vueghs
Post by Koen Vueghs
SQL server
*) The error occurs on two different systems
*) MDAC 2.6 with latest SP
*) We are using TCP/IP as communication layer
*) Searches on the internet shows more people with
this
Post by Koen Vueghs
Post by Koen Vueghs
problem but no answers are given
.
.
.
Asaf
2003-07-15 15:00:39 UTC
Permalink
Koen, I am struggling with the same problem as well... (i know the
feeling).
so far it looks like most of the postings are pointing to a network
issue or something like that. I will update this thread if I will find
anything. if you can send me a quick note when you found the problem,
Post by Koen Vueghs
Yep, it is driving me crazy.....
Val Mazur
2003-07-16 01:30:15 UTC
Permalink
Hi,

Yes, all the KB articles, which somehow related to that kind of error, point
to the network problem. In some KBs it is relate specifically with using
TSP/IP address in connection

--
Val Mazur
Microsoft MVP
Post by Asaf
Koen, I am struggling with the same problem as well... (i know the
feeling).
so far it looks like most of the postings are pointing to a network
issue or something like that. I will update this thread if I will find
anything. if you can send me a quick note when you found the problem,
Post by Koen Vueghs
Yep, it is driving me crazy.....
Koen Vueghs
2003-07-16 09:36:33 UTC
Permalink
Yesterday we discovered that the transaction LOG was not
backed up (I will kick the installers *ss)and had grown
till 23GB

Anyway since I put the transaction LOG backup into action
we only had 1 ConnectionWrite logging. (no connectionread)

I really do NOT think is has anything to do with the
network because we had the problem on 2 separate
production systems which are on different locations.

So the status is now better... if no ConnectionRead
problem will occur before tomorrow morning the issue is
solved for me.

To be complete I would like to add that we also had
locking problems which also seems to be solved now.

I will post the result tomorrow.
-----Original Message-----
Koen, I am struggling with the same problem as well... (i
know the
feeling).
so far it looks like most of the postings are pointing to
a network
issue or something like that. I will update this thread
if I will find
anything. if you can send me a quick note when you found
the problem,
Thanks!
Roy Fine
2003-07-15 16:40:43 UTC
Permalink
Koen

You are definitely seeing a network problem. recv is a function in the
WinSock2 library. WinSock2 is the API programming interface for socket
programming - and is commonly used in TCP/IP environments...

The more common error return codes from recv in a stable application
would be WSAECONNRESET or WSAETIMEDOUT, or WSAECONNABORTED. If you have
a lot of noise on the network, there will be a lot of retries, and when
the retry threshold limit is reached, the underlying communications
protocol will just give up and return an error -- unfortunately, the
errors are often, as they are propagated back up the protocol stack,
filtered and the real underlying problem is often covered up...

To start the troubleshooting process, I would be suspect of just about
everything from the network adapter on computer A to the network adapter
on computer B (wires, connectors, hubs, switches, the NIC cards in the
two endpoint computers, other offending NIC cards, etc). To effectively
diagnose/trouble shoot, you need to FIRST fire up Performance monitor
and start two counters on the network adapter on each of the two
endpoint machines (the client and the server) -- look at
PacketReceivedErrors and PacketOutboundErrors counters -- watch these
two counters on each of the two machines for a couple of days ..

In addition, you should install Network Monitor on the Server (NetMon
can be installed only on a Win2K server) - and look at MAC Error
Statistics for a couple of days... If you see a lot of errors, then
start replacing hardware.

If you are the network admin for your network, these are tools that you
MUST have! If you have a network admin, you need to get them involved
ASAP...

I hope this helps.

regards
roy fine
Post by Koen Vueghs
Source = Microsoft OLE DB Provider for ODBC Drivers,
Description = [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionRead (recv()).
*) We are using Win2K SP3 and a seperate W2K Server with
SQL server
*) The error occurs on two different systems
*) MDAC 2.6 with latest SP
*) We are using TCP/IP as communication layer
*) Searches on the internet shows more people with this
problem but no answers are given
Koen Vueghs
2003-07-16 11:42:35 UTC
Permalink
Thank you for thinking with me.

As I posted above, at this moment the cause of my troubles
seemed to be the transaction log file.

The network-scenario seems indeed the logical problem but
the problem exists on two separate (brand new) systems.
When the problem does return I will certainly use your
advice and start monitoring the network.

Kind regards,
Koen
-----Original Message-----
Koen
You are definitely seeing a network problem. recv is a
function in the
WinSock2 library. WinSock2 is the API programming
interface for socket
programming - and is commonly used in TCP/IP
environments...
The more common error return codes from recv in a stable
application
would be WSAECONNRESET or WSAETIMEDOUT, or
WSAECONNABORTED. If you have
a lot of noise on the network, there will be a lot of
retries, and when
the retry threshold limit is reached, the underlying
communications
protocol will just give up and return an error --
unfortunately, the
errors are often, as they are propagated back up the
protocol stack,
filtered and the real underlying problem is often covered
up...
To start the troubleshooting process, I would be suspect
of just about
everything from the network adapter on computer A to the
network adapter
on computer B (wires, connectors, hubs, switches, the NIC
cards in the
two endpoint computers, other offending NIC cards, etc).
To effectively
diagnose/trouble shoot, you need to FIRST fire up
Performance monitor
and start two counters on the network adapter on each of
the two
endpoint machines (the client and the server) -- look at
PacketReceivedErrors and PacketOutboundErrors counters --
watch these
two counters on each of the two machines for a couple of
days ..
In addition, you should install Network Monitor on the
Server (NetMon
can be installed only on a Win2K server) - and look at
MAC Error
Statistics for a couple of days... If you see a lot of
errors, then
start replacing hardware.
If you are the network admin for your network, these are
tools that you
MUST have! If you have a network admin, you need to get
them involved
ASAP...
I hope this helps.
Koen Vueghs
2003-07-17 07:02:18 UTC
Permalink
Ok that's it!!

No problems for 2 days now...

I guess the direct cause of the problem was the
transaction log file of 23 GByte.
Since we started backing it up and changed it back to a
normal size all our connectionread errors (and lock
problems) seem to be solved!

I do not really understand how this solution is related
with the connectionread errors but I think it has
something to do with the performance of the SQL server.

Val Mazur and Roy Fine: Again thanks a lot for searching a
solution with me.
-----Original Message-----
Source = Microsoft OLE DB Provider for ODBC Drivers,
Description = [Microsoft][ODBC SQL Server Driver]
[DBNETLIB]
ConnectionRead (recv()).
*) We are using Win2K SP3 and a seperate W2K Server with
SQL server
*) The error occurs on two different systems
*) MDAC 2.6 with latest SP
*) We are using TCP/IP as communication layer
*) Searches on the internet shows more people with this
problem but no answers are given
.
Koen Vueghs
2003-07-18 12:14:57 UTC
Permalink
DAMN,

Problem just occured again! Started monitoring the network!
rlfine
2003-07-18 22:52:50 UTC
Permalink
Koen,

lots of luck, mate...

regards
roy fine
Post by Koen Vueghs
DAMN,
Problem just occured again! Started monitoring the network!
Loading...