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

Applies To
SQL Server 2012 Developer SQL Server 2012 Enterprise SQL Server 2012 Standard SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use)

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.

Recommendation: Install the latest cumulative update for SQL Server

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:

      

Status

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