We help IT Professionals succeed at work.

[DBNETLIB][ConnectionRead (recv()).]General network error.

Rob4077
Rob4077 asked
on
4,035 Views
Last Modified: 2008-06-12
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 once every 5 seconds
3 There are 8 other threads running that are linked to the database 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?
Comment
Watch Question

Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Thanks icemokka,
What you're saying makes sense but what didn't make sense to me was that the server and client are on the same machine. Anyway I spent some time looking at possible causes and finally found that Norton's Firewall allowed transactions accross TCP/IP 192.168.0.148 for hours then suddenly decided one of the comms was a Trojan virus at work and killed the connection. I turned the firewall off and so far it's worked fine. Now I just have to figure out how to get Norton's to work properly.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.