Re: Internal connection fatal error
From: Max Metral (memetral_at_hotmail.com)
Date: 07/31/04
- Next message: DaberElay: "how to read excel data into a dataset"
- Previous message: Miha Markic [MVP C#]: "Re: Insert CLOB into Oracle using ADO.NET"
- In reply to: Max Metral: "Internal connection fatal error"
- Next in thread: William \(Bill\) Vaughn: "Re: Internal connection fatal error"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 31 Jul 2004 11:06:38 -0400
The words "sucks" and "SQL Server" are starting a slow walk towards each
other. For *now*, rebooting the db machine seems to have eradicated these
errors, although the load may not have reached similar heights since it's a
weekend.
"Max Metral" <memetral@hotmail.com> wrote in message
news:OPsOqrmdEHA.3212@TK2MSFTNGP12.phx.gbl...
> I've seen other posts about such errors, but never a solution. It seems
to
> appear randomly under load. We are pretty vigilant about "using"
> IDataReader's and Connections, so it's pretty unlikely that we're doing
> something outwardly wrong that would excuse this sort of behavior. The
> stack is:
>
> TARGETSITE: System.Data.SqlClient.SqlDataReader
> ExecuteReader(System.Data.CommandBehavior,
> System.Data.SqlClient.RunBehavior, Boolean)
>
> STACKTRACE: at
> System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior,
> RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteReader()
> at Web.MyPage.Page_Load(Object sender, EventArgs e)
> <removed by me>
>
> Perhaps related, we also see random errors like this about columns we KNOW
> exist in recordsets that are being returned:
>
> MESSAGE: EventId
> SOURCE: System.Data
> TARGETSITE: Int32 GetOrdinal(System.String)
> STACKTRACE: at System.Data.Common.FieldNameLookup.GetOrdinal(String
> fieldName)
> at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
> at MyObject..ctor(IDataReader eventReader, EventData eventData)
> <removed by me>
>
> This is definitely unacceptable behavior from ADO, SQL Server, or both...
No
> code that an end user writes in a managed language should be able to
create
> this kind of untraceable havoc.
>
> Any thoughts?
>
>
- Next message: DaberElay: "how to read excel data into a dataset"
- Previous message: Miha Markic [MVP C#]: "Re: Insert CLOB into Oracle using ADO.NET"
- In reply to: Max Metral: "Internal connection fatal error"
- Next in thread: William \(Bill\) Vaughn: "Re: Internal connection fatal error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
