Re: ADO.NET & MS SQL 2000 - General Network Error
- From: "Sahil Malik [MVP]" <contactmethrumyblog@xxxxxxxxxx>
- Date: Thu, 20 Oct 2005 11:06:29 -0400
Rob,
I found a very exhaustive answer by an MS Person,
http://groups.google.com/group/microsoft.public.sqlserver.programming/msg/7f3bcc3e8bbb331e?hl=en&lr=&ie=UTF-8&oe=UTF-8&rnum=9
Maybe it'll help. It does mention conditions similar to yours. Maybe a
better answer is to create a webservice that is closer to the database? I'm
not sure if that is a workable option in your case though.
- Sahil Malik [MVP]
ADO.NET 2.0 book -
http://codebetter.com/blogs/sahil.malik/archive/2005/05/13/63199.aspx
-------------------------------------------------------------------------------------------
"Rob R. Ainscough" <robains@xxxxxxxxxxx> wrote in message
news:eleA$wL1FHA.3560@xxxxxxxxxxxxxxxxxxxxxxx
>I have a .NET Windows application that works perfectly (no errors) when it
>communicates with my SQL Server locally (LAN). The exact same application
>when executed on another PC outside our LAN (via Broadband connection) will
>start to generate the following error:
>
> Description:
> 11: System.Data.SqlClient.SqlException: General network error. Check your
> network documentation.
> at System.Data.SqlClient.SqlDataReader.InternalClose(Boolean
> closeReader)
> at System.Data.SqlClient.SqlDataReader.Close()
> at System.Data.SqlClient.SqlConnection.CloseReader()
> at System.Data.SqlClient.SqlConnection.Close()
>
> The problem appears to be random yet consistant, meaning it will happen
> consistantly but never at the same point. And then sometimes it will
> clear itself up and then continue processing and sometimes not.
>
> The ONLY variable in the equation is LAN vs. Broadband connection. LAN
> connection to the SQL Server never generates any errors. Broadband
> connection to the SQL Server will generate the above errors at random
> intervals.
>
> I've tried the following "guess work" solutions I found via Google search:
>
> Pooling=False
> Max Pool Size = 300
> Connect Timeout=90
> Turn off Indexing Services
>
> None of these resolve the problem. I've also checked and double checked
> my code (even as far as putting a trace on the code) to make sure any data
> readers are closed -- the only common thing I've noted is that a data
> reader is always somehow involved -- it is as if the data reader (ADO.NET)
> requires a high speed connection (aka LAN) to function reliably. If the
> data reader is placed on a low speed connection it becomes
> unreliable/unstable.
>
> http://weblogs.asp.net/ssadasivuni/archive/2003/12/06/41705.aspx
>
> At least I know I'm not alone in this problem.
>
> Rob.
>
>
.
- Follow-Ups:
- Re: ADO.NET & MS SQL 2000 - General Network Error
- From: Rob R. Ainscough
- Re: ADO.NET & MS SQL 2000 - General Network Error
- Prev by Date: Re: memory&handles growth due to not disposing command?
- Next by Date: SQL Server 2000 SELECT COUNT(*) Issue
- Previous by thread: RE: ADO.NET & MS SQL 2000 - General Network Error
- Next by thread: Re: ADO.NET & MS SQL 2000 - General Network Error
- Index(es):
Relevant Pages
|
