General network error

  • Thread starter Thread starter Valerie Hough
  • Start date Start date
V

Valerie Hough

Hi
I am supporting a client that gets 5-10 of the following errors each day:

General network error. Check your network documentation.

-----------------------------

Stack trace:

at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction)

at
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString
options, Boolean& isInTransaction)

at System.Data.SqlClient.SqlConnection.Open()



They are running SQLServer 2000 on a Windows 2003 Server domain.



The applications always use the following connection string:

"Server=MySqlServer;Integrated Security=SSPI;Pooling=true;Initial
Catalog=MyDatabase"


Someone has verified that:

- every SqlConnection.Open() has a corresponding SqlConnection.Close()

- every SqlReader.ExecuteReader() has a corresponding SqlReader.Close()



All code is enclosed in try/catch blocks - there are no other exceptions
occurring



One blog I found suggested turning off pooling, another suggested setting
Max Pool Count to some very high number like 5000.



I would very much like to understand the cause of the problem before I start
trying things at random.



Can anyone help?



Thanks in advance.

Valerie Hough
 
Hi

A while ago, I had that problem too.
I had set the CommandTimeOut of all my Command objects and I have added
Pooling=False to my connection string.


--


HTH

Éric Moreau, MCSD, Visual Developer - Visual Basic MVP
Conseiller Principal / Senior Consultant
Concept S2i inc. (www.s2i.com)
http://emoreau.s2i.com/
 
Thanks for the reply.

What did you set your CommandTimeOut to? Did it depend on the quantity of
data expected?

Also, with pooling set to false, did this increase the time it took for your
s/w to complete its operations? Was it noticeable to the end user?

Thanks again.
 
Hi

I don't have access to the client code that has this error but I think I
have set the CommandTimeOut to 90.
Also, with pooling set to false, did this increase the time it took for
your s/w to complete its operations? Was it noticeable to the end user?
Click to expand...

It is an application use by about 50 users and nothing noticeable by users.

At least they can run without any errors and this is noticeable.

--


HTH

Éric Moreau, MCSD, Visual Developer - Visual Basic MVP
Conseiller Principal / Senior Consultant
Concept S2i inc. (www.s2i.com)
http://emoreau.s2i.com/
 
Back
Top