FIX: SQL Server may shut down when you use Service Broker in SQL Server 2012 or SQL Server 2014

Applies to: SQL Server 2012 DeveloperSQL Server 2012 EnterpriseSQL Server 2012 Standard More

Symptoms


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.

Cause


This issue occurs because of a race condition in SQL Server 2012 or SQL Server 2014 Service Broker.

Resolution


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.

Status


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