SQL Server 2012: A severe error occurred on the current command.

SQL Server 2012: A severe error occurred on the current command. by Kjell Gunnarsson

Resolved

as Fixed

Type:	Bug
ID:	777759
Opened:	1/29/2013 6:23:43 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Executing the statement below in a Store procedure generates exception i SQL Server.
(biSeqNo is a bigint column).

select @biFirst = min(biSeqNo)
from dbo.TNT_Log
where biSeqNo >= @biSeqNoFirst

Problem reproduced in SQL2012 RTM, SQL2012 SP1 and SQL2012 SP1 + CU2.

Details (expand)

English

SQL Server 2012 - Enterprise Edition

SQL Engine

Windows Server 2008 R2 (all editions) (SP1)

US English

I got a script that creates the table, adds 3 indexes and a store procedure that contains the "select min" statement.

Table is filled with 150000 rows before the SP is called.

(Script can be sent by mail is Microsoft is interested)

Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

@biFirst should be returned via a select statement.

X64

File Name	Submitted By	Submitted On	File Size
SQL2012_Exception_Reproduced.zip	Kjell Gunnarsson	1/30/2013	606 KB
SQLDump0055.txt	Kjell Gunnarsson	1/30/2013	62 KB
SQLDUMPER_ERRORLOG.log	Kjell Gunnarsson	1/30/2013	352 KB
Dumpfiles.zip (restricted)	Kjell Gunnarsson	1/30/2013	-
SQL2012_Exception_Reproduced.zip (restricted)	Kjell Gunnarsson	1/30/2013	-

Posted by Microsoft on 4/22/2013 at 2:32 PM

Closing the loop. See my previous comment.

--
Umachandar, SQL Progrmmability Team

Posted by Microsoft on 4/11/2013 at 8:43 AM

Hello,
The fix will go in the next service pack for SQL Server 2012. Thanks again for reporting the issue.

--
Umachandar, SQL Progrmmability Team

Posted by Kjell Gunnarsson on 4/10/2013 at 11:27 PM

Ok, got the message that this problem has been solved. When will the next service pack be released that includes the solved problem ?.

Posted by Microsoft on 2/1/2013 at 11:33 AM

Thanks for confirming that the problem reproes on the latest builds too. We will take a look at this & let you know.

--
Umachandar

Posted by Kjell Gunnarsson on 1/31/2013 at 10:54 PM

Problem reproduced in SQL2012 RTM, SQL2012 SP1 and SQL2012 SP1 + CU2.

Posted by Microsoft on 1/31/2013 at 11:21 AM

Thanks for the files. We will take a look at it. Also, please install the latest service pack for SQL Server 2012 & the cumulative updates optionally to see if the problem persists.

You can find SQL Server 2012 Service Pack 1 below:

http://www.microsoft.com/en-us/download/details.aspx?id=35575

--
Umachandar

Posted by Kjell Gunnarsson on 1/30/2013 at 11:26 PM

Script that reproduces the problem as well as dumpfiles has now been sent to Microsoft as attached files.

Posted by Microsoft on 1/30/2013 at 3:22 PM

Hello,
Thanks for reporting the issue. The error message indicates that you hit some AV or other serious bug in our code. If you look in the LOG directory of the SQL Server installation, you will find some mini dump files & log files. Can you please attach that to the bug? This will help us troubleshoot the problem further. If you have a repro script that will help too.

--
Umachandar, SQL Programmability Team