BUG: Execution of Non-Existent Procedure May Trap Server

ID: Q116292

The information in this article applies to:

Microsoft SQL Server version 4.2x

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          : kbprg kbbug4.20 SSrvWinNT 
Version           : 4.2
Platform          : WINDOWS 
Issue type        :

Last Reviewed: March 19, 1999