OLE DB error: OLE DB or ODBC error: [DBNETLIB][ConnectionRead (recv()).]General network erro

Hi guys,

Anyone encountered this type of error " OLE DB error: OLE DB or ODBC error: [DBNETLIB][ConnectionRead (recv()).]General network error"

The error you saw is quit common and it can be mapped to many cases. In most cases, the error happens because the server closes the connection for some reason when client is expecting data from the server. Can you described more about you app? Does the error happen during a long running query? Is the error consistent or intermittent.|||

Hello!!!

The application is a Business Intelligence application, wherein lots of extract transformation and loading process are involved before processing the cube. The error is intermittent and happens during the dimension processing. Our server is running Win2k3 sp1 sql server 2005 sp1 also configured with 8 GB memory and AWE enabled.

What we are doing in order to continue the process is to either restart sql server service or the analysis service and process the dimension that failed.

any idea on what is causing the error?

|||

Hi Larry,

General Network Error is a infamous error and one of the toughest cases MS PSS faces nowadays. This is due to there can be various cause of this problem.

There is a webcast on this topic:

http://support.microsoft.com/kb/875285/en-us

I remember there is a common cause of GNE for windows 2003 sp1, but can not find the KB now. Maybe I will find and post it here when I get back to work on Monday for your reference.

Thx, -Justin

|||

Tnx Justin, It will be great and I'll appreciate it if you can post the KB here.

Thanks,

Larry

|||

Here is the KB. This is a general cause of GNE on Win2003 SP1.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;899599

Basically, GNE occurs when the client connection is unexpectedly closed. This mostly due to temporarily network hardware failure or firewall related issue.

|||

In case of your cube application, one of the possibility is that the server decided to close a connection for one of the following reason. (1) query exection was too long, you can extend the connection timeout value to mitigate the issue. (2) your failed query, thus the connection, was choosen as a deadlock victim and killed by the server.

If you are using SQL Server 2005, you might find interesting entries in ERRORLOG to correlate your GNE. For two reasons that I listed above, the better forum to ask how to identify them is from sql server engine forum.