FIX: Commit Causes an Assertion and the SQL Server Program Stops Responding or Closes (319212)
The information in this article applies to:
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: <xdesmgr.c>, 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).
RESOLUTIONA 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: 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.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Minor | Last Reviewed: | 10/18/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE kbSQLServ700preSP5fix KB319212 |
---|
|