Error: -2147217900

Howdy People,

If there is a FAQ for this, could someone point me to it, otherwise, here is
my problem.

I'm running an extremely simple (or so I though) vbscript which uses ADO to
update an SQL Server table from a text file. The script reads the file line
by line and for each line it performs a delete on the database with a
statement like the following:

DELETE FROM MyTable WHERE MyField = '3794'

What could be simpler eh? In a table containing over 3000 rows, 8 rows fail
with the following error code:

-2147217900

There is so error source or description. Each time it is the same 8 queries
which fail. The statements which fail can be run just fine using Query
Analyzer.

I'd be grateful for any thoughts.

Mike BPerhaps it could that the rows dont exist in the
SQL Server table, or perhaps that you have
duplicate records somewhere.

What results does the following script return:

select myField, count(*)
from mytable
group by myField
having count(*)>1
order by 2 desc

Pete Brown
Falls Creek
Oz

"mike netspace.net.au>" <transam@.<REMOVETHISINCLUDINGBRACKETS> wrote in
message news:400736db$1@.dnews.tpgi.com.au...
> Howdy People,
> If there is a FAQ for this, could someone point me to it, otherwise, here
is
> my problem.
> I'm running an extremely simple (or so I though) vbscript which uses ADO
to
> update an SQL Server table from a text file. The script reads the file
line
> by line and for each line it performs a delete on the database with a
> statement like the following:
> DELETE FROM MyTable WHERE MyField = '3794'
> What could be simpler eh? In a table containing over 3000 rows, 8 rows
fail
> with the following error code:
> -2147217900
> There is so error source or description. Each time it is the same 8
queries
> which fail. The statements which fail can be run just fine using Query
> Analyzer.
> I'd be grateful for any thoughts.
> Mike B
>
>

Error: 17805, Severity: 20, State: 3 Invalid buffer received from client.

Howdy Folks,
Our site has been experiencing this issue for a couple of months now.. Hopefully someone else can assist, as Ive got to a point where I think issue lies within the application or a Microsoft bug. Web searches have reveled a number installations that have also had this error but its has not revealed an actual fix.

I understand this error code basically means data being returned to the client is getting either corrupted or the data is too large to fit into the buffer on the client side. Client in our case is the terminal server, here after called a application server

As the user base has increased form 5 to 20, I have noticed that the issue is occurring more frequently in comparison to when the company first started using the application /database. Its just about daily now...

The db server also has 8 other db's residing on it - but they are all less than 300 meg.

The attached PowerPoint doc has the trace info & the surrounding code for each process that has suffered a buffer error over a period of a week.

DB Server Environment: Win2000 SP4, SQL2000 SP3a, MDAC 2.7 SP1 refresh.
Application Environment: Written In house in VB.NET Framework 1.1 setup as a published app on a terminal server running windows 2000 SP4

Common features of the issue, that have been omitted from trace output for visibility reasons are:
- Involves 1 particular DB (thats accessed by VB app) & its developement db
- All connections are coming from 1 application server
- Issue does not relate to any particular site connecting to the application server using this application

I have reviewed & fixed several potential server side causes but this error still is occuring with in the environment:

MDAC versions must be common on application & server:
- Removed from equation by updating MDAC version on App server to be the same as DB Server: 2.7 SP1 Refresh

Network related
- Considered unlikely; we are also not experiencing network card errors on either server; also all db's would be experiencing connectivity errors.

Which leaves us with Application related options to review:
- Compilation error of application
- App parameter definitions to stored procedures are the correct data type
- Ensure values being passed do not exceed 4000 characters as that has also been known to create this error message
- I've asked the developer to review MS KB 827366 article, as it may be a valid test
- In regard to MSKB 832977 - I am not using pssdiag & have a later version of the MS Analyzer. But what I thought was interesting, is the statement that this problem occurs more frequently when an application submits a large remote procedure call (RPC) input buffer, especially when the RPC input buffer is greater than or equal to 8 KB. However, this problem may occur even if the input buffer is less than 4 KB
- A is using datatypes varchar & char - not nvarchar & nhar

Any assistance with this issue would be appreicated as server performance is being effected - these processes hang around for 1 - 5 mins before terminating (refer duration times in the powerpoint traces)

Thanks In advance

Suze.I think Reads column referrs to physical reads. If that's the case then the number is pretty high and may be the reason for the client timeout. Sporadic behavior of the same query may be caused by inconsistent execution plan generated. Do you use dynamic SQL a lot?|||Thank you for your question...

The number of reads appears only on the first slide, the other 7 don't have any reads - just the really long duration.
Because of this long duration & the audit logout entry for the same process id directly after the buffer error, I've assumed that the process is timing out. But in saying that users are not reporting that they have been kicked out of the application or receiving any error messages - so maybe way off in that assumption.

We are using SP's passing in parameter's. The developer reckons this means its not being built at runtime. As you might be able to tell, I'm a newbie - so I don't know if this means they are dynamic sql or not... are you able to advise.

Best Regards|||The 4000-limit was revealed in my previous environment when SP3 was applied. The FE code was...of course, JAVA, what else can cause this. And they were parsing the call to the stored procedure without TYPEing the parameters, which resulted in every character-based parameter to be interpreted as NVARCHAR. Now, the article (827366) is also referring to the possibility of data type size misalignment, where the value supplied may be outside of the boundaries allowed for a specific data type (just a hunch).|||I like the sound of your hunch. Unfortunately I can't provide the developer any proof - being a newbie in all. Anyway, I think I've done the next best thing by sending the developer the MSKB article 827366 again & Ant profiler to use so he can see what his code is doing - hopefully this will give him the visibility he needs.

Thanks again & Best Regards
Suze.

Error: 1105, Severity: 17, State: 2

Hi ,

I have a SQL Server 2000 database on my C drive.

Over the weekend my C drive got full due to my transaction log files ballooning up.

At that point none of my users were able to log into their the VB application and enter data.

I freed up some disk space, and then the users were able to log in fine, except for a certain column variable(aggregate) values were negative.

I deattached the DBs and Ldf files and made copies of them on to a test envirnoment. Within the test environment, I ran SQL Query Analyzer with SQL statments that did give me the aggregate values as negative. This matched my VB application values aswell.

I ran

DBCC CHECKDB -- no errors

DBCC DBREINDEX -- no errors

Our programming vendor tells us the DBs are corrupt.

From Error file

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2007-01-30 19:43:56.95 spid52 C:\Program Files\Microsoft SQL Server\MSSQL\Data\tempdb.mdf: Operating system error 112(There is not enough space on the disk.) encountered.

2007-01-30 19:43:56.98 spid52 Error: 1105, Severity: 17, State: 2

2007-01-30 19:43:56.98 spid52 Could not allocate space for object '(SYSTEM table id: -900439724)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full..

2007-02-23 09:56:21.21 spid56 C:\Program Files\Microsoft SQL Server\MSSQL\Data\ActgSQL.mdf: Operating system error 112(There is not enough space on the disk.) encountered.

2007-02-23 09:56:21.24 spid56 Error: 1105, Severity: 17, State: 2

2007-02-23 09:56:21.24 spid56 Could not allocate space for object 'POSInventory' in database 'ActgSQL' because the 'PRIMARY' filegroup is full..

2007-02-23 11:11:09.74 spid56 Error: 1105, Severity: 17, State: 2

2007-02-23 11:11:09.74 spid56 Could not allocate space for object 'POSInventory' in database 'ActgSQL' because the 'PRIMARY' filegroup is full..

2007-02-23 15:50:19.27 spid59 Process ID 53 killed by hostname ORCHID, host process ID 3360.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I thought I had backups but I don t. So now I m in a big bind. Help!!

Any suggestions ?

No.. i don't think your database is corrupted. the only thing is that it could not have able to commit the transaction done when there was no space in the desk.. if your statement are not concluded in BEGIN TRAN / COMMIT TRAN.. some data inconsistancy may occur... As such the database may not be corrupted as a whole. This is a common problem when there is no DBA or DBA background person around. You need to keep a track of all backups which u r taking and also TL and TempDb growth etc..

Madhu

error with c# select statement

hi i have copied this from my other page where it works fine and i cant understand what is going wrong! maybe one of your guys can point out what i cant see! herei s my code

string strOrderID = Request.QueryString["orderID"].ToString();

int intOrderID =Convert.ToInt32(strOrderID);

int intCustID =Convert.ToInt32(Request.QueryString["qsnOrderCustID"].ToString());

lblCustomerID.Text = Request.QueryString["qsnOrderCustID"].ToString();lblOrderID.Text = Request.QueryString["orderID"].ToString();

SqlConnection myConn =newSqlConnection("Data Source=xxxx;Initial Catalog=xxxx;User ID=xxxx;Password=xxxx");

//This is the sql statement.

string sql ="SELECT [del_address], [del_post_code], [del_time] From tbl_del WHERE order_ID = " + intOrderID;

//This creates a sql command which executes the sql statement.

SqlCommand sqlCmd =newSqlCommand(sql, myConn);

myConn.Open();

SqlDataReader dr = sqlCmd.ExecuteReader();

//This reads the first result from the sqlReader

dr.Read();

try

{

lblDelTime.Text =Convert.ToString(dr["del_time"].ToString);

lblDelAddy.Text = dr["del_address"].ToString();

lblDelPCode.Text = dr["del_post_code"].ToString();if (lblDelAddy.Text !="")

{

lblDelDate.Visible =true;

lblDelTime.Visible =true;

Label1.Visible =true;

Label2.Visible =true;

}

}

catch (Exception except)

{

lblerror.Text =Convert.ToString(except);

}

Regards

Jez

What error are you getting?

|||

try

{

lblDelTime.Text =Convert.ToString(dr["del_time"].ToString);

lblDelAddy.Text = dr["del_address"].ToString();

lblDelPCode.Text = dr["del_post_code"].ToString();if (lblDelAddy.Text !="")

{

lblDelDate.Visible =true;

lblDelTime.Visible =true;

Label1.Visible =true;Label2.Visible =true;

}

}

catch (Exception except)

{

lblerror.Text =Convert.ToString(except);

}

I can only find the above problem in the code...if you can name the error it will be more helpful for us.

|||

i realised that i was being a complete idiot (thats what being up for to long does! makes you miss the obvious!) i took a look at the bigger picture, it said that the textbox wasnt being filled, so maybe a problem with the data reader, no, but because i have 2 data readers on one page and i just copied and pasted the code, i forgot to put dr2[" instead of dr["