Microsoft KB Archive/307541

From BetaArchive Wiki
Knowledge Base


FIX: Error 1203 and Failed Assertion Occurs When You Run a Query with a Parallel Plan

Article ID: 307541

Article Last Modified on 6/29/2004



APPLIES TO

  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 7.0 Service Pack 1
  • Microsoft SQL Server 7.0 Service Pack 2
  • Microsoft SQL Server 7.0 Service Pack 3



This article was previously published under Q307541

BUG #: 101982 (SQLBUGS_70)

SYMPTOMS

A query that uses a parallel plan and requires lock escalation may fail with the following type of error message:

Error: 1203, Severity: 20, State: 1 Process ID 14 attempting to unlock unowned resource TAB: 8:1922105888 []..

The error message is followed by a stack dump that is written to the SQL Server error log for the following assertion:

SQL Server Assertion: File: <proc.c>, line=1931 Failed Assertion = 'm_activeSdesList.Head () == NULL'.

At this point, an abnormal termination of SQL Server may occur.

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 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:

   Version      File name
   --------------------------

   7.00.1008    Sqlservr.exe
                

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


WORKAROUND

To work around this problem either:

  • Use the MAXDOP hint set to 1 for the query that encounters the problem. -or-


  • Change the max degree of parallelism configuration option to 1.


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.

Keywords: kbbug kbfix kbsqlserv700presp4fix KB307541