FIX: RPC Using SQL_PARAM_OUTPUT and SQL_PARAM_DEFAULT May Cause AV

Article translations Article translations
Article ID: 223257 - View products that this article applies to.
This article was previously published under Q223257
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 54840 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

The SQL Server process may experience multiple exceptions, generally access violations (AVs), and/or may stop unexpectedly if the first invocation of a given procedure is an SQL remote procedure call (RPC) event using the SQL_PARAM_OUTPUT and SQL_PARAM_DEFAULT bindings during initial submittal.

WORKAROUND

To work around this problem, do either of the following:
  • Update the application to avoid the use of the SQL_PARAM_DEFAULT option.

    -or-
  • Drop and re-create the procedure, adding the WITH RECOMPILE directive to the creation script. The following is an example:
    create procedure spTest @strData char(80) = "RD"
    WITH RECOMPILE
    as
    begin
       select 1
    end

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 223257 - Last Review: October 20, 2013 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB223257

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com