Article ID: 2444085 - Last Review: January 17, 2011 - Revision: 2.0

FIX: "Transaction is already aborted (WinMgmt)" error when you run DTC transactions from BizTalk Server 2009 to SQL Server 2008 or SQL Server 2008 R2 if event notifications are enabled

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Microsoft distributes Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2008 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 2008 R2 and Microsoft SQL Server 2008 fix release.

On This Page

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You install Microsoft BizTalk Server 2009 on a computer.
  • You install Microsoft SQL Server 2008 or SQL Server 2008 R2 on another computer.
  • You configure SQL Server 2008 or SQL Server 2008 R2 to be a back-end server for BizTalk Server 2009.
  • You enable event notifications in SQL Server 2008 or SQL Server 2008 R2.
  • You run some Distributed Transaction Coordinator (DTC) transactions that are sent to SQL Server 2008 or SQL Server 2008 R2 and that are from BizTalk Server 2009.

In this scenario, you may receive the following error message on the computer that is running BizTalk Server 2009:
Transaction is already aborted (WinMgmt)
Also, an event that resembles the following is logged in the Windows log file on the computer that is running SQL Server 2008 or SQL Server 2008 R2:
Source: MSSQL$SSDB01
Event ID: 17065
Task Category: Server
Level: Error
Description: SQL Server Assertion: File: <purecall.cpp>, line = 51 Failed Assertion = '!"purecall"' Pure virtual function call. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Source: MSSQL$SSDB01
Event ID: 8565
Task Category: Server
Level: Error
Description: SQL Server failed to prepare DTC transaction. Failure code: 3602.
Additionally, a mini-dump file is generated in Application log file, and the following error message is logged in the SQL Server Error log file:
SqlDumpExceptionHandler: Process 22 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 09/01/10 14:12:50 spid 22
*
*
* Exception Address = 0000000000000000 Module(UNKNOWN+0000000000000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 0000000000000000
Back to the top

RESOLUTION

Cumulative update information

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 12 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2467236  (http://support.microsoft.com/kb/2467236/LN/ ) Cumulative update package 12 for SQL Server 2008 Service Pack 1
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 2008 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:
970365  (http://support.microsoft.com/kb/970365/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2438347  (http://support.microsoft.com/kb/2438347/ ) Cumulative Update package 5 for SQL Server 2008 R2
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 2008 R2 fix release. We recommend 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:
981356  (http://support.microsoft.com/kb/981356/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2467239  (http://support.microsoft.com/kb/2467239/LN/ ) Cumulative update package 2 for SQL Server 2008 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 2008 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:
2402659  (http://support.microsoft.com/kb/2402659/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 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.
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top

REFERENCES

For more information about the event notifications for the database engine in SQL Server 2008 R2, visit the following Microsoft Developer Network (MSDN) website:
General information about the event notifications for the database engine in SQL Server 2008 R2 (http://msdn.microsoft.com/en-us/library/ms182602.aspx)

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897  (http://support.microsoft.com/kb/935897/ ) An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499  (http://support.microsoft.com/kb/822499/ ) New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Workgroup
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Workgroup
Back to the top
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2444085
Back to the top