Service Broker Error in SQL 2012

Question

Hi all,

we have a Service Broker application that has been running stable on SQL 2005 for many months.  Now we are in the process of migrating to SQL 2012, and are encountering errors with Service Broker. 

Instance A on server 1 communicates with instance B on server 2 via service broker.  Instance A sends messages to instance B, and instance B also sends messages to instance A.  When we start up our SQL Server 2012 instances, the service broker messaging runs fine for a while, sometimes for hours, sometimes for a few days, then an error occurs on instance B:

Using 'dbghelp.dll' version '4.0.5'
***Stack Dump being sent to E:\Program Files\Microsoft SQL Server\MSSQL11.STAGING2\MSSQL\LOG\SQLDump9924.txt
SqlDumpExceptionHandler: Process 24 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

and then
Error: 9642, Severity: 16, State: 4.
An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 2905, State: 2. (Near endpoint role: Initiator, far endpoint address: '<ip of server1>')

When the error occurs, the transmission queue contains 2 entries for each conversation, one with the message to be sent, and one end of dialog.  Transmission status has the message:
An internal exception occurred while dispatching a message: Error: 2905, State: 2.

A profile trace shows on the initiator of the conversation:
Broker:Connection 2 - Connected
Broker:Connection 4 - Closing    An internal exception occurred while dispatching a message: Error: 2905, State: 2. 
Broker:Connection  5 - Closed

on the receiver of the conversation:
Broker:Connection 6 - Accept
Broker:Connection 4 - Closing    The connection was closed by the remote end, or an error occurred while receiving data: '64(The specified network name is no longer available.)'
Broker:Connection  5 - Closed

I don't get any Audit Broker Conversation events in the trace.

After that initial error, all successive conversations fail with the same error; I haven't found a way to clear up the problem short of restarting SQL Server.  After restarting both instances, all is well again, and messages are being sent and received.  Some hours or days later, the error occurs again. 

On our SQL 2012 servers we have cumulative update 4 installed.  We haven't had this problem on our SQL 2005 servers (sp3).  We have set designated broker endpoints on each server.

Any insight would really be appreciated.

 

 

Answer 1

Is there anyone can help on this issue?

Answer 2

Could you please run the SSBDIAGNOSE utility for the service broker set up in Question, both for checking issues with the configuration, as well as issues with a specific conversation. Please follow this link for details on how to use SSBDIAGNOSE for generating a report of the issues - http://msdn.microsoft.com/en-us/library/bb934450.aspx

The report from SSBDIAGNOSE should help us better investigate the problem and suggest a solution.

---

Sanil Mhatre | Database Developer | MCTS | If you find my reply useful in any way, please vote it as helpful. If it has helped answer your question, please mark it as Answer. http://sqlwithsanil.com

Answer 3

Hi "charlotte_b", just checking if you got a chance to run SSBDIAGNOSE on your service broker setup, or maybe found another solution to the issue ?

Thanks

---

Sanil Mhatre | Database Developer | MCTS | If you find my reply useful in any way, please vote it as helpful. If it has helped answer your question, please mark it as Answer. http://sqlwithsanil.com