FIX: AV Assigning Decimal from VIEW to OUTPUT Parameter

Last reviewed: April 9, 1997
Article ID: Q156862
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5
BUG #: 15623 (Windows NT: 6.0)
       15860 (Windows NT: 6.5)

SYMPTOMS

Assigning a decimal value from a VIEW to an OUTPUT parameter of a stored procedure causes a handled access violation (AV). The client reports the AV message on SQL Server version 6.0, and appears to stop responding on SQL Server version 6.5. The errorlog contains the details of the access violation.

WORKAROUND

To work around this problem, do one of the following:

  • Avoid assigning the decimal datatype OUTPUT parameter to a stored procedure.
  • Avoid using views; select directly from the underlying tables.
  • Instead of using OUTPUT parameters, return values from the stored procedure.
  • Create a temporary table to hold the results of the SELECT statement. Then assign the results to OUTPUT parameters, selecting data from the temporary table.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

MORE INFORMATION

This problem happens only when the decimal value is selected from a view and assigned to an OUTPUT parameter of a stored procedure. The process is terminated by the server. On SQL Server 6.5, the client does not report the error, so it appears to stop responding.


Additional query words:
Keywords : kbbug6.00 kbbug6.50 kbfix6.50.sp2 kbnetwork SSrvErr_Log SSrvGPF
Version : 6.0 6.5
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 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.