Select the product you need help with
FIX: Unhandled exception when you use a marked transaction that spans multiple databases in SQL Server 2008 R2 or in SQL Server 2012Article ID: 2749913 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 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 Service Pack 1 fix release. On This PageSymptomsConsider the following scenario:
Date Time spid # ex_raise2: Unhandled exception raised, major=32, minor=60, state=1, severity=16, attempting to create symptom dump Date Time spid # Using 'dbghelp.dll' version '4.0.5' Date Time spid # **Dump thread - spid = 0, EC = 0x0000000162A44B20 Date Time spid # ***Stack Dump being sent to Drive :\Program Files\Microsoft SQL Server\MSSQL10_50.R2_RTM\MSSQL\LOG\SQLDump0022.txt Date Time spid # * ******************************************************************************* Date Time spid # * Date Time spid # * BEGIN STACK DUMP: Date Time spid # * Time Stamp spid 24 Date Time spid # * Date Time spid # * ex_raise2: Unhandled exception raised, major=32, minor=60, state=1, severity=16 Note You may experience the same issue when you try to synchronize backups by using a marked transaction that spans multiple databases in Microsoft Visual Studio Team Foundation Server. CauseThis issue occurs because the allocation of an internal buffer fails when multiple databases are involved in the same marked transaction. Note Marked transaction information is saved in the msdb.dbo.logmarkhistory table. This table contains one row for each committed marked transaction. ResolutionCumulative update informationCumulative Update 2 for SQL Server 2012 SP1The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:2790947 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 2012 SP1 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:
(http://support.microsoft.com/kb/2790947/
)
Cumulative update package 2 for SQL Server 2012
Service Pack 12772858
(http://support.microsoft.com/kb/2772858/
)
The SQL
Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was
releasedCumulative Update 5 for SQL Server 2012The 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 2012, click the following article number to view the article in the Microsoft Knowledge Base:2777772 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 2012 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:
(http://support.microsoft.com/kb/2777772/
)
Cumulative update package 5 for SQL Server 20122692828
(http://support.microsoft.com/kb/2692828/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was releasedCumulative Update 4 for SQL Server 2008 R2 SP2The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:2777358 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 SP 2 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:
(http://support.microsoft.com/kb/2777358/
)
Cumulative update package 4 for SQL Server 2008 R2 Service Pack 2
2730301
(http://support.microsoft.com/kb/2730301/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released
SQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:2756574 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 Service Pack 1 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:
(http://support.microsoft.com/kb/2756574/
)
Cumulative update package 9 for SQL Server 2008 R2 Service Pack 12567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was releasedStatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. More informationFor more information about how to back up Visual Studio Team Foundation Server, go to the following MSDN website: How to back up Team Foundation Server For more information about marked transactions, go to the following MSDN website:
(http://msdn.microsoft.com/en-us/library/ms253070.aspx)
General information about marked transactions
(http://msdn.microsoft.com/en-us/library/ms187014(v=sql.105).aspx)
PropertiesArticle ID: 2749913 - Last Review: January 24, 2013 - Revision: 6.0 Applies to
| Article Translations
 |
Back to the top
