Microsoft KB Archive/319212

= FIX: Commit Causes an Assertion and the SQL Server Program Stops Responding or Closes =

Article ID: 319212

Article Last Modified on 10/18/2005

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q319212



BUG #: 102436 (SQLBUG_70)



SYMPTOMS
If a SQL Server connection (system process ID [SPID]) performs a data definition language (DDL, for example, it modifies a database object's structure by creating an index or renaming an object) operation and the DDL operation modifies the data in a temp table in a single transaction while another SPID commits changes to a table, the first SPID may raise an assertion error while trying to commit. After the assertion occurs, a handled access violation occurs. In some cases, after the access violation occurs, the SQL Server service may stop responding. In other circumstances, an unhandled exception may follow the assertion and cause the SQL Server service to shut down.

This text is logged to the SQL Server error log: 2001-07-30 01:20:08.38 kernel SQL Server Assertion: File: , line = 818 Failed Assertion = 'xlockinfo.IsLockListEmpty ' closexdes: lock list not empty. 2001-07-30 01:20:08.38 spid12 Error: 3624, Severity: 20, State: 1. The line number in this example is from SQL Server 7.0 Service Pack 3 (SP3).



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:   Version      File name       Description --

7.00.1023   Sqlservr.exe    SP3-based hotfix NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

You must apply this hotfix to a server that is running SQL Server 7.0 Service Pack 3. This fix will not be available in Service Pack 4; however, it will be made available in a post-SP4 build.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
The initial symptom of the problem is an assertion like the one that follows (the stack is taken from SQL Server 7.0 Service Pack 3 [SP3]). The function calls under XCB::Commit may differ from the sequence shown here. ************************************************************************* - Short Stack Dump 0x77f67a2b Module(ntdll+7a2b) (ZwGetContextThread+b) 0x0078a1d0 Module(sqlservr+38a1d0) (utassert_fail+1a0) 0x005b2260 Module(sqlservr+1b2260) (XDES::Close+f3) 0x0040bf68 Module(sqlservr+bf68) (XCB::Commit+368) 0x0042ac99 Module(sqlservr+2ac99) (CStmtXactEnd::XretExecute+81) 0x0040f487 Module(sqlservr+f487) (CMsqlExecContext::ExecuteStmts+11b) 0x0040ef35 Module(sqlservr+ef35) (CMsqlExecContext::Execute+16b) 2001-07-30 01:20:08.38 kernel  SQL Server Assertion: File: , line = 818 Failed Assertion = 'xlockinfo.IsLockListEmpty ' closexdes: lock list not empty. 2001-07-30 01:20:08.38 spid12  Error: 3624, Severity: 20, State: 1.
 * BEGIN STACK DUMP:
 * Input Buffer 60 bytes -
 * I F  @ @ T R A N C O U N T   >   0   C O M M I T   T R A N

Keywords: kbbug kbfix kbqfe kbsqlserv700presp5fix kbhotfixserver KB319212

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.