August 20, 2009 at 11:32 pm
hi all,
i'm getting this waring from the production server:
Warning: Fatal error 3624 occurred at Aug 19 2009 10:30AM. Note the error and time, and contact your system administrator. A severe error occurred on the current command. The results, if any, should be discarded. Location: tmpilb.cpp:2530 Expression: fFalse SPID: 145 Process ID: 1260 Description: Attempt to access expired blob handle (3)
please help me out why this waring is comming?
🙂
August 20, 2009 at 11:35 pm
When exactly are you getting this warning..?
August 20, 2009 at 11:44 pm
Check the following link.
August 20, 2009 at 11:45 pm
i don't know exact functional area, but how can i prevent it.
Warning: Fatal error 3624 occurred at Aug 19 2009 10:30AM. Note the error and time, and contact your system administrator. A severe error occurred on the current command. The results, if any, should be discarded. Location: tmpilb.cpp:2530 Expression: fFalse SPID: 145 Process ID: 1260 Description: Attempt to access expired blob handle (3)
A severe error occurred on the current command
how can i know the which command is .
🙂
August 21, 2009 at 12:15 am
hi thanks for ur post,
but in this article Error as:
DateTimeSPID Error: 17065, Severity: 16, State: 1.
DateTimeSPID SQL Server Assertion: File: , line = 2565 Failed Assertion = 'fFalse' Attempt to access expired blob handle (3). This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
DateTimeSPID Error: 3624, Severity: 20, State: 1.
DateTimeSPID A system assertion check has failed. Check the SQL Server error log for details
but it is not the error what i posted.
thanks
🙂
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply