Microsoft KB Archive/940935

= FIX: Error message when you run a query that is associated with a parallel execution plan in SQL Server 2005: &quot;SQL Server Assertion: File: , line=10850 Failed Assertion = 'GetLocalLockPartition == xactLockInfo->GetLocalLockPartition '&quot; =

Article ID: 940935

Article Last Modified on 8/17/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Workgroup Edition

-



Bug #: 50001589 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.



SYMPTOMS
Consider the following scenario. You have a computer that is running SQL Server 2005 and has multiple processors. You connect to the instance of SQL Server 2005, and you start a distributed transaction. Then, you create a second connection to the instance. The second connection enlists to the previously created distributed transaction, and the connection runs a query that is associated with a parallel execution plan. In this scenario, the parallel query may fail. Additionally, a minidump file is generated. The following error message is logged in the SQL Server 2005 error log:

SQL Server Assertion: File: , line=10850 Failed Assertion = 'GetLocalLockPartition == xactLockInfo->GetLocalLockPartition '.



CAUSE
This problem occurs because SQL Server objects that are associated with Distributed Transaction Management are not synchronized.



RESOLUTION
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



WORKAROUND
To work around this problem, disable parallel plan generation. To do this, set the max degree of parallelism option to 1. To do this, run the following statements: sp_configure 'show advanced options', 1; GO RECONFIGURE WITH OVERRIDE; GO sp_configure 'max degree of parallelism', 1; GO RECONFIGURE WITH OVERRIDE; GO Note If you use this method to work around this problem, SQL Server performance may decrease.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2

