The Service Broker endpoint is in disabled or stopped state.

Question

The Service Broker endpoint is in disabled or stopped state.

Bilal H. Bhatt 136

Hello,

We have SQL 2019 shared AG instance hosting many databases. We are getting lots of below messages.

The Service Broker endpoint is in disabled or stopped state.

Please help

LiHongMSFT-4306 31,576 Reputation points

2023-03-10T08:31:31.0766667+00:00

Hi @Bilal H. Bhatt

Do you have further question on this issue, could we offer more support?

If any answer helps on your issue, you could mark it as answer so other user with similar problem could see this easier. :)

Best regards,

Cosmog Hong

2 answers

Your answer

LiHongMSFT-4306 31,576 Reputation points

2023-03-10T08:31:31.0766667+00:00

Hi @Bilal H. Bhatt

Do you have further question on this issue, could we offer more support?

If any answer helps on your issue, you could mark it as answer so other user with similar problem could see this easier. :)

Best regards,

Cosmog Hong

Answer 1

Ronen Ariely 15,206

Hi,

(1) All machines with Availability Groups must have the Service Broker endpoint exists and correctly configured. Use the following query to confirm you have Service Broker endpoint:

SELECT name, protocol_desc, type_desc, state_desc, port
FROM sys.tcp_endpoints
WHERE type_desc = 'SERVICE_BROKER';

Go over the following document: https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/service-broker-with-always-on-availability-groups-sql-server?view=sql-server-ver15&WT.mc_id=DP-MVP-5001699

In most cases, you simply need to CREATE ENDPOINT

(2) If the above did not solve your issue then please check what is the exact version of he server (please check @@VERSION)

Bilal H. Bhatt 136 Reputation points

2023-02-19T11:41:56.13+00:00
Thanks..

does creating the ENDPOINT cause any kind of issue.. if i use below command to create the ENDPOINT?

CREATE ENDPOINT [SH2ENDPOINT] STATE = STARTED AS TCP (LISTENER_PORT = 4022, LISTENER_IP = ALL ) FOR SERVICE_BROKER (AUTHENTICATION = WINDOWS)
Erland Sommarskog 122.3K Reputation points MVP Volunteer Moderator

2023-02-19T11:55:52.7366667+00:00

All machines with Availability Groups must have the Service Broker endpoint exists

Judging from the grammar, it appears that you have been reading http://slavasql.blogspot.com/2019/11/errorlog-flooded-with-service-broker.html :-)

My reading of the article you link to (and which was in the abovementioned blogpost) that you need a Service Broker endpoint, if you are using Service Broker and you have a service with communication to other nodes. Not that you need to have a Service Broker endpoint, just because you have an AG.

I found a few posts which said that these messages can be ignored, for instance http://sqlserverdbahelp-naresh.blogspot.com/2016/01/the-service-broker-endpoint-is-in.html But they are from unknown sources, so I would not take them as authoritative.

Then again, you don't want a message that litters your errorlog every 15 minutes. And it seems corny if they print this message as a matter of routine, with no proof of Service Broker being active. (I don't have access to an AGto check if that is the case.) So presumably, there is something in Bilal's AG that uses Service Broker, and will remain unfunctional until that endpoint is created.
Ronen Ariely 15,206 Reputation points

2023-02-23T09:49:17.6833333+00:00

@Erland Sommarskog , it might be a bug or issue in my side but all the links in your comment are not active. I click on it and nothing happen

I checked the HTML code and it is clear why the links are not really link to anywhere

Hi Bilal H. Bhatt

(1) Off-topic: I recommend you to change your display name a but since the system does recognize it well (I think the issue is the dot in the name). Try to add message and use @ and your name, the system do not find the name. In fact it does not find any name that start with "Bilal H." which is why I think the dot is the issue - itg should be checked.

(2) Regarding the question, I will not advice directly what to do in such cases in a forum since I do not have the full information and I am not familiar with the specific system.

In general as much as I understand this should be the solution for your case. I can say that in your place with only the information that you gave us, this will be the solution that I will try

I can always DROP the ENDPOINT if needed

Answer 2

Hi @Bilal H. Bhatt

The Service Broker endpoint is in disabled or stopped state.

For most cases, you might ignore this message.

If you need service in an Availability Group to receive remote messages, then the CREATE ENDPOINT code you post is needed. Besides, you need ensure that the availability group possesses a listener, and the Service Broker endpoint exists and is correctly configured.

See: Requirements for a Service in an Availability Group to Receive Remote Messages.

Best regards,

Cosmog Hong

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Share via

The Service Broker endpoint is in disabled or stopped state.

2 answers

Your answer