The Service Broker endpoint is in disabled or stopped state

  • I have a SQL 2012 Enterprise edition HADR cluster with 2 nodes and my event log on the second node (current primary for the AG) is being filled with these messages

    The Service Broker endpoint is in disabled or stopped state

    I wasn't able to find too much on the issue. I did find this one open Microsoft connect bug report from back in April 2013 http://connect.microsoft.com/SQLServer/feedback/details/783219/alwayson-the-service-broker-endpoint-is-in-disabled-or-stopped-state

    Anyone ever have this issue? Any ideas on what might be causing it?

    Let me know what other details I can provide to help figure this out.

    O/S: Windows 2012

    SQL Server 2012 v11.0.3412

    Currently 1 AG with 1 DB

  • I am seeing the same message in the errorlog.

    SQL Server 2012 (11.0.3373). We are using AlwaysOn AG's and have configured and are using the AG Listener for read only traffic.

    I do not seem to be experiencing any issues as a result of the message but it would be nice to identify the cause of the message.

  • I am also having the same issue.

    The error message shows in the SQL Server logs, and appears once every 15 minutes.

    I have a SQL 2012 SP2.

  • This was removed by the editor as SPAM

  • This was removed by the editor as SPAM

  • This was removed by the editor as SPAM

  • I am getting this alert in SQL 2016 SP1 CU7.

    I don't have any issues reported and can not find anything wrong. 

    Found this on stackexchange.

    http://sqlserverdbahelp-naresh.blogspot.com/2016/01/the-service-broker-endpoint-is-in.html
    It’s a default behavior. The message will show when AlwaysOn availability group Listener is created and SQL Server binds the Listener’s IP dynamically. There is no method to suppress the message. These messages are informational message and do not cause any harm and can safely be ignored.

  • You do realize that this is a 4 year old thread, and the OP has not been active for 2 years???

    Michael L John
    If you assassinate a DBA, would you pull a trigger?
    To properly post on a forum:
    http://www.sqlservercentral.com/articles/61537/

  • Just because I'm not actively posting doesn't mean I'm not still monitoring 🙂

  • I created a service broker endpoint in a test environment out of curiosity where these messages were occurring and this resolved the issue.

    CREATE ENDPOINT BrokerEndpointTest

    STATE = STARTED

    AS TCP ( LISTENER_PORT = 4022 )

    FOR SERVICE_BROKER (AUTHENTICATION = WINDOWS );

    GO

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply