BUG: Execution of Non-Existent Procedure May Trap Server

Last reviewed: April 29, 1997
Article ID: Q116292

The information in this article applies to:

Microsoft SQL Server, version 4.2

BUG# NT: 808 (4.2)

SYMPTOMS

When an application attempts to execute a non-existent stored procedure on a Windows NT SQL Server using the DB-Library (DB-Lib) remote procedure call (RPC) APIs, SQL Server terminates with an access violation.

CAUSE

This behavior will only occur under certain circumstances. The behavior seems to be dependent on the name specified in dbrpcinit() and the number of parameters specified in dbrpcparam() calls. This behavior does not occur when issuing RPC requests against ODS applications or OS/2 SQL Servers.

WORKAROUND

Ensure that the stored procedure being executed exists on the SQL Server.

STATUS

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

Additional query words: Windows NT
Keywords : kbbug4.20 kbprg SSrvWinNT
Version : 4.2
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: April 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.