Re: Column <ColumnName> does not belong to table <TableName>
- From: cori <cori@xxxxxxxxxxxxxxxx>
- Date: Wed, 17 Jan 2007 22:56:00 -0800
Um, yes, thanks. Searching for 80070057 *does* return hits - I should have
explained a little better, perhaps.
It seems that error code 80070057 is somewhat of a generic error code. I've
seen it in my own code on occasion in a variety of situations - COM+ problems
and other types of data access issues caused by my own foolishness. None of
those are applicable in this case as far as I can tell, and indeed, none of
the hits on the search you pointed to are relevant to the specific issue I'm
experiencing. The most applicable one is "Standard COM Error 80070057. One
or more arguments are not valid error." Except that all the arguments *are*
valid since the column in question is in the table in question.
I threw the 80070057 message in there in the interests of completeness, but
I don't think it's the central issue. In fact, when you add the other part
of the error message I quoted to your search (the "System.Data" part that I
posted) you get 4 hits, none of which match.
If we assume that perhaps the error message is being generated by invliad
arguments, it begs the question: why are the arguments invalid? - the column
*does* belong to the table.
--
Thanks;
cori
"Cor Ligthert [MVP]" wrote:
Cori,.
You told there was no information on internet but this simple search on MSDN
gives quiet a few pages of text with answers.
http://lab.msdn.microsoft.com/search/refinement.aspx?__VIEWSTATE=&query=80070057
Cor
"cori" <cori@xxxxxxxxxxxxxxxx> schreef in bericht
news:69CDF19A-3941-4746-8D45-59EF1F284EF1@xxxxxxxxxxxxxxxx
Hello all;
We're using ADO.Net on a classic ASP site that's using a .Net dll for
backend data manipulation. Every so often we receive an error in the
pattern
in the subject line, where the column name and table name change depending
on
what page is being accessed. The error also includes the text
"System.Data
error '80070057'". The entire site is inaccessible when this error
occurs,
with every user receiving that error message, and restarting IIS resolves
the
issue. Without fail, the column mentioned in the error is actually being
populated into the dataset respresented by the table name mentioned.
I've seen several mentions of this issue when googling, and a few in the
MSDN newsgroups, but have never seen a confirmed resolution. Has anyone
else
resolved this?
--
Thanks;
cori
- References:
- Re: Column <ColumnName> does not belong to table <TableName>
- From: Cor Ligthert [MVP]
- Re: Column <ColumnName> does not belong to table <TableName>
- Prev by Date: Re: ADO.net Orcas Samples Install Problem
- Next by Date: Re: DataRowVersion.Original and RowState quesions.
- Previous by thread: Re: Column <ColumnName> does not belong to table <TableName>
- Next by thread: Re: DataRowVersion.Original and RowState quesions.
- Index(es):
Relevant Pages
|