invalid BLOB handle in record buffer
Posted: Mon 25 Feb 2008 12:40
Hi,
My program runs at about 200 sites. At a couple of them, I keep
getting this error "Invalid blob handle in record buffer". This error
occurs just now and then, a couple of times per day, but afterwards,
the contents of TEXT fields may get mixed up with those of other
records. Of course, this causes serious problems.
Setup: Delphi 2006, DbExpress TClientdataset, latest corelab driver, MS SQL 2005 standard.
It's basically one table with about 8 TEXT fields of
100 fields total, 2000 records. Changing to varchar(max) does not
help, I presume the problem is on the client, not on the server.
About 10 simulteanous users.
--> I can not reproduce this in a controlled situation.
--> I do not know when EXACTLY the error occurs, e.g. what the user is
doing and which method of the clientdataset is begin invoked. It's a
large system. The dataset state appears to be dsEdit.
I'm looking for pointers in the right direction or anyone who has experienced this before. I can't tell for sure whether this problem is in the corelab driver or elsewhere.
Thanks for any pointer in the right direction.
Willem van de Vis
My program runs at about 200 sites. At a couple of them, I keep
getting this error "Invalid blob handle in record buffer". This error
occurs just now and then, a couple of times per day, but afterwards,
the contents of TEXT fields may get mixed up with those of other
records. Of course, this causes serious problems.
Setup: Delphi 2006, DbExpress TClientdataset, latest corelab driver, MS SQL 2005 standard.
It's basically one table with about 8 TEXT fields of
100 fields total, 2000 records. Changing to varchar(max) does not
help, I presume the problem is on the client, not on the server.
About 10 simulteanous users.
--> I can not reproduce this in a controlled situation.
--> I do not know when EXACTLY the error occurs, e.g. what the user is
doing and which method of the clientdataset is begin invoked. It's a
large system. The dataset state appears to be dsEdit.
I'm looking for pointers in the right direction or anyone who has experienced this before. I can't tell for sure whether this problem is in the corelab driver or elsewhere.
Thanks for any pointer in the right direction.
Willem van de Vis