FIX: SQL Server may shut down when you use Service Broker in SQL Server 2012 or SQL Server 2014
Assume that you use Service Broker in Microsoft SQL Server 2012 or SQL Server 2014. When you send messages of different priorities to more than one target service from the initiator, an access violation may occur, and SQL Server shuts down.
This issue occurs because of a race condition in SQL Server 2012 or SQL Server 2014 Service Broker.
The issue was first fixed in the following cumulative updates of SQL Server.
Note The fix for this issue is enhanced in CU9 for SQL Server 2012 SP2.
- Cumulative Update 4 for SQL Server 2014 SP1
- Cumulative Update 11 for SQL Server 2014
- Cumulative Update 9 for SQL Server 2012 SP2
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 3051145 - Last Review: 12/22/2015 02:57:00 - Revision: 4.0
Microsoft SQL Server 2012 Service Pack 2, Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Standard, Microsoft SQL Server 2014 Service Pack 1
- kbqfe kbfix kbsurveynew kbexpertiseadvanced KB3051145