Home » Php » php – What causes SQL Server to return the message 'The statement has been terminated'?

php – What causes SQL Server to return the message 'The statement has been terminated'?

Posted by: admin July 12, 2020 Leave a comment


I have a very simple INSERT statement being executed from a PHP script running on a Linux Apache web server. I can run the query fine from within SQL Management Studio and it normally runs fine from PHP as well. However, every once in awhile I get an error message from my PHP script that the query failed and the mssql_get_last_message() function returns ‘The statement has been terminated’.

What sources can cause this message to be returned from SQL Server?

How to&Answers:

You have found one of the most annoying parts of SQL Server. There are situations where an error can be raised, and SQL will generated two error messages: the first to explain what the error was, and the second to say something useful like “The statement has been terminated” (which, technically, is error number 3621). The thing is that SQL, and most everything else that touches it–such as PHP–can only see/pick up/process/or otherwise utilize that last unlcear error message. The one that’s actually useful gets lost.

The quick way to figure out what’s going on is to run the sequence of commands leading up to the error from SSMS. This, apparently, will not work for you.

A fussier way to figure it out is to fire up SQL Profiler to track the Exception event, and then run your process. This should show all errors that occured. Tossing in relevant other events (SP:Starting, SP:StmtStarting, SQL:BatchStarting, whatever is applicable to the code your submitting to the database) will show which command is raising the error.


To get a numeric error code from mssql you can do a select that looks something like

Which SHOULD return the correct error code.

You can also try this code which is posted on PHP.NET.

function query($sQuery, $hDb_conn, $sError, $bDebug)
    if(!$rQuery = @mssql_query($sQuery, $hDb_conn))
        $sMssql_get_last_message = mssql_get_last_message();
        $sQuery_added  = "BEGIN TRY\n";
        $sQuery_added .= "\t".$sQuery."\n";
        $sQuery_added .= "END TRY\n";
        $sQuery_added .= "BEGIN CATCH\n";
        $sQuery_added .= "\tSELECT 'Error: '  + ERROR_MESSAGE()\n";
        $sQuery_added .= "END CATCH";
        $rRun2= @mssql_query($sQuery_added, $hDb_conn);
        $aReturn = @mssql_fetch_assoc($rRun2);
            echo $sError.'. MSSQL returned: '.$sMssql_get_last_message.'.<br>Executed query: '.nl2br($sQuery);
            echo $sError.'. MSSQL returned: '.$aReturn['computed'].'.<br>Executed query: '.nl2br($sQuery);
        return FALSE;
        return $rQuery;


You can use the code in the message to know which is the error. For example:

[2627: The statement has been terminated.]

In this case, the error code is 2627, so if you execute the sql below you’ll know the message

SELECT msg.text
  FROM sys.messages msg 
 INNER JOIN sys.syslanguages lng ON lng.msglangid = msg.language_id
 WHERE msg.message_id = 2627
   AND lng.alias = 'English'

Violation of %ls constraint ‘%.*ls’. Cannot insert duplicate key in
object ‘%.*ls’. The duplicate key value is %ls.

This is a way to know the right message error. In my example the error is violation of primary key