FIX: Various issues occur when a database is involved in a database mirroring session and in a transactional replication if trace flag 1448 is enabled

Consider the following scenario:

• You configure a database for database mirroring in Microsoft SQL Server 2005, Microsoft SQL Server 2008, or Microsoft SQL Server 2008 R2.
• The database is also a publication database in a transaction replication.
• Trace flag 1448 is enabled.

In this scenario, you may encounter one or more of the following problems:

• Data is not replicated successfully.
• When automatic failover occurs, the role switch is delayed. The two databases in the database mirroring session are displayed as the principal database.
• Error messages that resemble the following may be logged in the SQL Server Errorlog file:

  <Date Time> Server      **Dump thread - spid = 0, PSS = 0x0000000000000000, EC = 0x0000000000000000              <Date Time> Server      ***Stack Dump being sent to <X>:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG \SQLDump0124.txt              <Date Time> Server      * *******************************************************************************              <Date Time> Server      *              <Date Time> Server      * BEGIN STACK DUMP:              <Date Time> Server      *   <Date Time> spid 0              <Date Time> Server      *              <Date Time> Server      * Non-yielding Resource Monitor              <Date Time> Server      *              <Date Time> Server      * *******************************************************************************              <Date Time> Server      * -------------------------------------------------------------------------------              <Date Time> Server      * Short Stack Dump              <Date Time> Server      Stack Signature for the dump is 0x0000000000000080              <Date Time> Server      Timeout waiting for external dump process 7032.              <Date Time> Server      Resource Monitor (0xb60) Worker 0x0000000003B081C0 appears to be non-yielding on Node 0. Memory  freed: 0 KB. Approx CPU Used: kernel 0 ms, user 0 ms, Interval: 61548.              <Date Time> spid<ID>     Error: 8509, Severity: 16, State: 1.              <Date Time> spid<ID>     Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: 0x8004d00e (error not found).              <Date Time> spid<ID>     Error: 8509, Severity: 16, State: 1.              <Date Time> spid119     Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: 0x8004d00e (error not found).              <Date Time> spid<ID>     Error: 8509, Severity: 16, State: 1.              <Date Time> spid<ID>     Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: 0x8004d00e (error not found).              <Date Time> spid<ID>     Error: 8509, Severity: 16, State: 1.

This problem occurs because of a race condition.

Cumulative update information

SQL Server 2005

The fix for this issue was first released in Cumulative Update 10 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: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: Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. 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 Service Pack 1

The fix for this issue was first released in Cumulative Update 9 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: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: 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 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 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: 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. 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:

SQL Server 2008 R2

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 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base: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:

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

For information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about trace flag 1448, click the following article number to view the article in the Microsoft Knowledge Base: For more information about Database Mirroring, visit the following Microsoft website:For more information about transactional replication, visit the following Microsoft website:
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base: For more information about new features and improvements in SQL Server 2005 Service Pack 3, visit the following Microsoft website: 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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: