Article ID: 314117 - Last Review: September 26, 2005 - Revision: 1.1

FIX: Prepare/Execute on Query May Cause Handled Access Violation in CSsNumeric::ConvertFromStr

View products that this article applies to.

This article was previously published under Q314117

BUG #: 102142 (SQLBUG_70)

SYMPTOMS

If you use Prepare or Execute to submit a a query batch that contains numeric constants, a handled access violation may occur that terminates the client connection that submitted the query batch and leaves other clients unaffected. In this case, the following output appears in the SQL Server error log:

2001-07-10 05:33:28.75 spid12   Using 'sqlimage.dll' version '4.0.5'
Stack Dump being sent to e:\sqldata\log\SQL00001.dmp
2001-07-10 05:33:37.20 spid12   Error: 0, Severity: 19, State: 0
2001-07-10 05:33:37.20 spid12   SqlDumpExceptionHandler: Process 12 
generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server
is terminating this process.
***************************************************************************
****
*  
* BEGIN STACK DUMP:
*   11/27/01 11:30:46 spid 7
* 
*   Exception Address = 004A4281 (CSsNumeric::ConvertFromStr + 132)
*   Exception Code    = c0000005 E

*   Access Violation occurred reading address 2FF00000

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301511 (http://support.microsoft.com/kb/301511/EN-US/ ) INF: How to Obtain the Latest SQL Server 7.0 Service Pack

NOTE: The following hotfix was created prior to Microsoft SQL Server 7.0 Service Pack 4.

The English version of this fix should have the following file attributes or later:


   Date         Time       Version     Size          File name
   ---------------------------------------------------------------

   2001-12-02   10:41 PM   7.00.1016   5,054,736 KB   Sqlservr.exe
   2001-01-14   12:39 AM   7.00.0978     586,000 KB   Sqlsort.dll

NOTE: Because of file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.

Back to the top