FIX: Infrequent Access Violation During LOAD TRANSACTION

Last reviewed: December 19, 1997
Article ID: Q170436
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16946 (6.5)

SYMPTOMS

You may infrequently experience a handled access violation (AV) during a LOAD TRANSACTION. If you are running a debug version of SQL Server 6.5 (needed to ensure an accurate stack trace), you can determine that this AV occurs in the ldxact() function.

If you use a LOAD DATABASE statement to reload the database and then use LOAD TRANSACTION to reapply the same transaction, the problem usually does not occur again.

The following is the stack trace from a 6.50.252 debug server:

   ldxact() + 0x178C
   s_execute() + 0x18FC
   sequencer() + 0x035C
   language_exec() + 0x06D6

WORKAROUND

To work around this problem, reload the database then reapply the same transaction files with LOAD TRANRANSACTION.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem was corrected in the latest Microsoft SQL Server 6.5 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K
Keywords          : kbbug6.50 SSrvGen SSrvGPF SSrvTran_SQL kbfix6.50.sp4 kbusage
Version           : 6.5
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix


================================================================================


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: December 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.