[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation

Question

[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation

Robbo

Old Hand

Points: 368
More actions
February 14, 2006 at 7:24 pm

#170598

I have a 3rd party application that is reading tables from SQL Server 2005 Express. Last night I set the program running on a continuous loop that reads values from a few tables, and updates a "heartbeat" record every few seconds - nothing else. This morning I found that after running for about 4 and a half hours it crashed with the following message:
Number = 0x80004004
Source = Microsoft OLE DB Provider for SQL Server
Description =[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.
SQL State = 08S01
NativeError = 11
I am running it on a machine operating on Windows XP Professional SP2 and the version of SQL Server 2005 I am running is 2005.090.1399.00. The 3rd party application is running on the same machine as SQL Server. The only systems that interrogate the table are:
1. The main program thread of the 3rd party application that does the work mentioned above.
2. A MS Access front end that interrogates some of the tables (linked) once every 5 seconds using an On Timer Event
3 There are 8 other threads running that are linked to the database on the 3rd party application but, when the application is idling as it was overnight, they do not interact with SQL tables at all.
There are a total of 7 tables, the largest having 99 records.
I have no idea what this message means or what to do to prevent it from happening. I chose SQL Server because I thought it was going to be robust but this is not inspiring confidence. Can anyone help me understand this message please?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Robbo Old Hand Points: 368 More actions · Answer 1

I think I can close this out as I suspect I have found the answer. Norton's antivirus seems to randomly conclude that the comms between client and server via TCP/IP is a Trojan Virus at work and stops it. I turned off the firewall and it appears to have fixed the problem. These comments are posted in case someone else has a similar problem.

milton_msu SSC Journeyman Points: 86 More actions · Answer 2

i m getting the same error but there is no norton installed on my machine .. so it could be some other problem

Robbo Old Hand Points: 368 More actions · Answer 3

It was a while ago but if I recall correctly I discovered what was causing the problem when I looked at the Event Viewer and found that Nortons was causing the problem. Have a look there and it may help you find the problem. In my case I changed to Trend Security and the problem never re-appeared.

Start>Control Panel>Administrative Tools>Event Viewer>System

Gift Peddie SSC Guru Points: 73570 More actions · Answer 4

You get this error because SQL Server 2005/8 Express, Express Advanced and Developer comes with most features disabled by default. In 2005 you have to go to SAC(surface area configuration tool) to enable TCP/IP and Named Pipes, enable local and remote connection. And in 2008 you go to Configuration manager and enable same. This is not available in VS2005/8 Express except VWD because web development require remote connection.

Kind regards,
Gift Peddie

Robbo Old Hand Points: 368 More actions · Answer 5

Thanks for your comments. In my case I don't think that was the problem as I had enabled those comms. My application would run for minutes to hours before this error would appear out of the blue. As soon as I changed away from Nortons the problem disappeared and hasn't reappeared since.