The information in this article applies to:
SYMPTOMSWhen 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. WORKAROUNDSet NOCOUNT OFF before calling the RAISERROR in the stored procedure, and then set NOCOUNT back ON after the RAISERROR. STATUSMicrosoft 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 : kbbug6.50 kbbug4.21 kbbug6.00 |
Last Reviewed: March 28, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |