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

This article was previously published under Q314117
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 102142 (SQLBUG_70)
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.dmp2001-07-10 05:33:37.20 spid12   Error: 0, Severity: 19, State: 02001-07-10 05:33:37.20 spid12   SqlDumpExceptionHandler: Process 12 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Serveris 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 				
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 theMicrosoft Knowledge Base:
301511 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.
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.

Article ID: 314117 - Last Review: 10/24/2013 08:55:27 - Revision: 1.1

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbsqlserv700presp4fix kbqfe kbhotfixserver KB314117