Error in blobman.cpp

I have just recently begun to experience a rather odd problem with a query
that has worked fine in the past. Now when I run it I get the following
error.
Server: Msg 3624, Level 20, State 1, Line 1
Location: blobman.cpp:2564
Expression: outBufLen >= inBufLen + OVERHEAD
SPID: 64
Process ID: 1240
Connection Broken.
Has anyone seen this error before? Is there any solution. I have been told
that there is a potential memory leak with the SQL Server 2000 by one of the
gentlemen monitoring our SQL Server. He says that he watches the memory for
the program slowly expand over the course of time until it forces a reboot
of the server machine. Could this be related?
Any help would be greatly appreciated.
Regards,
Daniel Hobert
Can you post your query with required information to repro it? Also check
the errorlog to see if you can find anything relevant to this error message.
It is possible that it could be a bug, however I have read about similar
errors occurring when using ALTER table ALTER column on text/image columns
which is not supported in SQL Server.
Anith
|||It's a simple select query, actually I've done a bit more research and it
appears as if this is the result of some corrupted indexes within the table
in question. I tried using dbcc checktable with the repair_all option but
it seems like the issues are such that I am going to have to do a repair and
risk losing some of the data in the table.
Thanks for the help,
Daniel
"Anith Sen" <anith@.bizdatasolutions.com> wrote in message
news:uLJWTvgiEHA.396@.TK2MSFTNGP12.phx.gbl...
> Can you post your query with required information to repro it? Also check
> the errorlog to see if you can find anything relevant to this error
message.
> It is possible that it could be a bug, however I have read about similar
> errors occurring when using ALTER table ALTER column on text/image columns
> which is not supported in SQL Server.
> --
> Anith
>
|||actually, it was the repair_rebuild option that I used and that didn't do
the trick. It seems like I'm going to have to use the
repair_allow_data_loss option and just hope that too much data wasn't lost.
- Daniel
"Daniel Hobert" <daniel@.cyberspacehq.com> wrote in message
news:412ba505$0$8088$a1866201@.newsreader.dsl.net.. .
> It's a simple select query, actually I've done a bit more research and it
> appears as if this is the result of some corrupted indexes within the
table
> in question. I tried using dbcc checktable with the repair_all option but
> it seems like the issues are such that I am going to have to do a repair
and[vbcol=seagreen]
> risk losing some of the data in the table.
> Thanks for the help,
> Daniel
> "Anith Sen" <anith@.bizdatasolutions.com> wrote in message
> news:uLJWTvgiEHA.396@.TK2MSFTNGP12.phx.gbl...
check[vbcol=seagreen]
> message.
columns
>
|||Have you run DBCC CHECKDB? If that is clean, then this is probably a bug.
Are you running SQL2000 SP3? It might help.
Wei Xiao
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Daniel Hobert" <daniel@.cyberspacehq.com> wrote in message
news:412b878a$0$65562$a1866201@.newsreader.dsl.net. ..
> I have just recently begun to experience a rather odd problem with a query
> that has worked fine in the past. Now when I run it I get the following
> error.
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: blobman.cpp:2564
> Expression: outBufLen >= inBufLen + OVERHEAD
> SPID: 64
> Process ID: 1240
> Connection Broken.
> Has anyone seen this error before? Is there any solution. I have been
told
> that there is a potential memory leak with the SQL Server 2000 by one of
the
> gentlemen monitoring our SQL Server. He says that he watches the memory
for
> the program slowly expand over the course of time until it forces a reboot
> of the server machine. Could this be related?
> Any help would be greatly appreciated.
> Regards,
> Daniel Hobert
>