Select the product you need help with
FIX: An access violation occurs in the "sqlservr!CSbMsgDispatcher::CSbReceivedDialog::AppendMsg" class in SQL Server 2008 R2 or in SQL Server 2012Article ID: 2649359 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 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 or Microsoft SQL Server 2012 fix release. On This PageSymptomsYou may encounter an access violation in the sqlservr!CSbMsgDispatcher::CSbReceivedDialog::AppendMsg class in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012. For example, you configure an instance of SQL Server 2008 R2 or SQL Server 2012 as a SQL Server Service Broker (SSB) to load an SSB message from several locations into a central database. An access violation occurs at the start of the load process. Additionally, SQL Server 2008 R2 or SQL Server 2012 stops working. ResolutionCumulative update informationSQL Server 2012The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2679368 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. 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:
(http://support.microsoft.com/kb/2679368/LN/
)
Cumulative update package 1 for SQL Server 20122692828 You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.
(http://support.microsoft.com/kb/2692828/LN/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released SQL Server 2008 R2 Service Pack 1The 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 SP1, click the following article number to view the article in the Microsoft Knowledge Base:2633146 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 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/2633146/
)
Cumulative Update package 4 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 released SQL Server 2008 R2The fix for this issue was first released in Cumulative Update 11. 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:2633145 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:
(http://support.microsoft.com/kb/2633145/
)
Cumulative Update package 11 for SQL Server 2008 R2981356
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was releasedStatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
ReferencesFor 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 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:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 2649359 - Last Review: November 19, 2012 - Revision: 4.0 Applies to
| Article Translations
|


Back to the top








