SQL SERVER – Msg 0, Level 11 – A Severe Error Occurred on the Current Command. The results, if Any, Should be Discarded

SQL
6 Comments

It’s always fun to fix something when there is no meaningful error message. As you can see in the blog title, message id = 0 and it doesn’t tell me how to fix the issue. Here is my checklist whenever someone reports below severe error:

It’s always fun to fix something when there is no meaningful error message. As you can see in blog title, message id = 0 and it doesn’t tell me how to fix the issue. Here is my checklist whenever someone reports below error:

CHECKLIST

  1. First and foremost, check database consistency. This can be done by running below command in SQL Server.
DBCC CHECKDB('database_name');
  1. If you have nailed down to a table, then check table consistency. We can execute below command
DBCC CHECKTABLE('table_name');
  1. Check the LOG folder which contains ERRORLOG and look for any file named ‘SQLDump*’ at the same time when the error was reported. If you find any, you can either contact Microsoft or use the self-service by getting dump analyzed using diagnostic preview.
  2. If you are getting this while using extended stored procedure, then you need to run, debug by running the exact piece of code one by one. Here is one such error which had none of 3 causes.

In case you want to see the error yourself, feel free to use below code

create table #ErrorLog (column1 char(8000))
go
insert into #ErrorLog
exec xp_readerrorlog 'SQL Error'
drop table #ErrorLog

Have you come across such error? What were the cause and solution?

Reference: Pinal Dave (https://blog.sqlauthority.com)

, , , ,
Previous Post
SQL SERVER – SQL Express Installation Error – Wait on the Database Engine Recovery Handle Failed
Next Post
SQL SERVER – Msg 3013 – Cannot Create Worker Thread. BACKUP LOG is Terminating Abnormally

Related Posts

6 Comments. Leave new

  • I got this error. what is solution

    Reply
  • Hariharan Ramalingam
    January 10, 2020 9:56 pm

    I’ve faced this issue. In my cause the database was in Synchronising state (AG 2016). Hence changed it from Async to Sync and the issue is resolved.

    Reply
  • Got this error during a Backup JOB which will run by the stored procedure

    Reply
  • Hi Pinal,

    can i run the error log code on production server
    it is very urgent.

    Reply
  • i am getting the same error while adding data file on my database. I am not able to add datafile on that database. What is the cause and what could be the solution

    Reply
  • flotsam7jetsam
    August 19, 2021 3:45 am

    Per Microsoft try DBCC CHECKDB() with TABLOCK

    Reply

Leave a Reply

Menu