BUG: Error Handler Not Called by RAISERROR if NOCOUNT Set ON

Last reviewed: May 5, 1997
Article ID: Q152135

The information in this article applies to:

Microsoft SQL Server, versions 4.21, 6.0 and 6.5

SYMPTOMS

When executing a stored procedure that raises an error through RAISERROR, the error handler in the DB-Library application is not called if NOCOUNT is set ON within the stored procedure. The message handler is always called correctly, but the calling of the error handler depends on the NOCOUNT behavior.

WORKAROUND

Set NOCOUNT OFF before calling the RAISERROR in the stored procedure, and then set NOCOUNT back ON after the RAISERROR.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.5, 6.0 and 4.21a. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: dblib proc
Keywords : kbbug4.21 kbbug6.00 kbbug6.50
Version : 4.21 6.0 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.