intermittent exceptions when accessing SQL data using ADO.NET

  • Thread starter Thread starter Matt
  • Start date Start date
M

Matt

hello

I have a web server win2000 SP4 accessing data on a SQL
server 2000 win2000 SP4 .NET 1.0

A ASP.NET app, using ADO.NET gets data using stored
procedures. There are many SP's called from many pages.
All data access is done through a class we wrote that can
return either datareaders or datasets depening on the
page.

The system can run for days without any data errors.

then, either one, or several errors can occur.
the errors can be generated when retrieving either
datareaders OR datasets, from a variety of pages, using a
variety of SP's. You can literally get a connection
problem, then refresh the page and it works!

typical exception:

SqlClient.SqlException General network error. Check your
network documentation.
at System.Data.SqlClient.SqlCommand.ExecuteReader
(CommandBehavior cmdBehavior, RunBehavior runBehavior,
Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader
(CommandBehavior behavior)

Has anyone seen anything like this before? It is SO hard
to nail down any conditions under which it is happening!

TIA
 
what kind of authentication are you using?
I've seen this problem when using Windows authentication to access a SQL
Server. If there are problems with the domain controller you end up having
trouble connecting to the DB.
 
Hi,thanks for your reply.

However, all access here is through SQL server
authentication, using the same connection string all the
time.

Matt
 
Are you using two different application or two copies of the same
application? In the last, see my post of 13/10/2003: I have a similar
problem.
 
Hi

Are you getting the same exceptions as I am?
Does it happen EVERY time you do it or just sometimes?

M
 
I've the error always when I start a second instance of the application.
The error is in fact not your: I have the connection object to nothing, but
the behavior seems similar.

See my posts fo more details.
 
Did you ever find a resolution to this problem. I am
starting to run into it.

Kevin
(e-mail address removed)
 
Back
Top