Running the following query in SQL Server Management Studio gives the error below.
update table_name set is_active = 0 where id = 3
In my case, I was using System.Threading.CancellationTokenSource
to cancel a SqlCommand
but not handling the exception with catch (SqlException) { }
In my case,I was using SubQuery
and had a same problem. I realized that the problem is from memory leakage.
Restarting MSSQL
service cause to flush tempDb
resource and free huge amount of memory.
so this was solve the problem.
I just had the same error, and it was down to a corrupted index. Re-indexing the table fixed the problem.
A different scenario but the same error: I got this error when I was trying to insert records into a temporary table using a stored procedure. It turned out there was a parameter mismatch. I was trying to insert a BIGINT into an INT.
Credit goes to Vicky Harp: http://vickyharp.com/2012/03/troubleshooting-a-severe-error-occurred-on-the-current-command/
There are 3 possibilities on the MS KB
When I see stuff like this: I always think hotfix, engine, server errors etc.
4 results: search for ""Msg 0, Level 11,State 0, Line 0" A severe error occurred on the current command"
Edit: It's on MS Connect too
Run DBCC CHECKTABLE('table_name');
Check the LOG folder where the isntance is installed (\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG
usually) for any file named 'SQLDUMP*
'