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:
- First and foremost, check database consistency. This can be done by running below command in SQL Server.
- If you have nailed down to a table, then check table consistency. We can execute below command
- 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.
- 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)