Symptoms
When you run a Microsoft SQL Server 2012 Service Broker application in SQL Server 2012, an access violation may occur, and error 2905 is logged in the SQL Server error log. The error details that are logged resemble the following:
Date Time spid# Using 'dbghelp.dll' version '4.0.5'
Date Time spid# ***Stack Dump being sent to <system drive>:\Program Files\Microsoft SQL Server\MSSQL11.STAGING2\MSSQL\LOG\SQLDump9217.txt
Date Time spid# SqlDumpExceptionHandler: Process 23 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Date Time spid# * *******************************************************************************
Date Time spid# *
Date Time spid# * BEGIN STACK DUMP:
Date Time spid# * Date Time spid#
Date Time spid# *
Date Time spid# *
Date Time spid# * Exception Address = 000007FEE8B8DBC8 Module(UNKNOWN+0000000000000000)
Date Time spid# * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
Date Time spid# * Access Violation occurred reading address 0000000000000010
Date Time spid# *
Date Time spid# *
Date Time spid# Error: 9642, Severity: 16, State: 4.
Date Time spid# An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 2905, State: 2. (Near endpoint role: Initiator, far endpoint address: '<IP address>')
Additionally, a dump file is generated in the SQL Server log folder.
Resolution
Cumulative update information
Cumulative Update 3 for SQL Server 2012 Service Pack 1 (SP1)
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012 SP 1, click the following article number to view the article in the Microsoft Knowledge Base:
2812412 Cumulative update package 3 for SQL Server 2012 Service Pack 1Note 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 SP 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:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
