INF: Proper Use for DB-Library Err Handler Return Code INT_EXIT

Last reviewed: February 10, 1998
Article ID: Q180779

The information in this article applies to:

Microsoft SQL Server, version 6.5

SUMMARY

This article describes how the INT_EXIT return code in the DB-Library error handler may cause unexpected application behavior.

For complete documentation on INT_EXIT, see the SQL Server Books Online.

MORE INFORMATION

INT_EXIT stops execution of the current process by invoking ExitProcess(1). This can lead to unexpected application behavior.

NOTE: You should NEVER use a return code of INT_EXIT when building extended stored procedures or COM-based components, especially in-process servers, ISAPI DLLs, or in other extensible architectures.

If you return INT_EXIT from your DB-Library message handler while in an extended stored procedure, the ExitProcess will simply stop the SQL Server process. There will be no message in the SQL Server errorlog and it appears as if someone turned off the computer.

Additional query words: crash shutdown db-lib
Keywords : SSrvProg
Version : WINNT:6.5
Platform : winnt
Issue type : kbinfo
Solution Type : Info_Provided

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: February 10, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.