The Configuration Manager administrator usually checks component statuses in the administration console. When they are shown in green, you can assume that everything is working properly. Sometimes, however, the opposite is true. The status of SMS_NOTIFICATION_SERVER is "green" in the console.
The BGBServer.log repeats the error:
The absence of a queue is an error, but this does not affect the status of the service. Checking the availability of TCP port 10123 shows no error. Closer inspection shows that in addition to the appearance of errors in the log, they do not work: CMPivot, scripts and actions called at the client, so the Notification mechanism is applied.
The cause is revealed by a check on the database server side:
As you can see, the culprit is the is_broker_enabled setting (should be 1). Of course, Configuration Manager's documentation clearly states that SQL Service Broker is to be enabled[1].
It is worth noting that since the 2010 version of Configuration Manager, you can figure out that you have an anomaly, the study of "Scenario health" will show in the case of SQL Server service broker overdue:
Earlier versions lacked such an examination, going further than just checking the SMS_NOTIFICATION_SERVER service.
[1]https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/configs/support-for-sql-server-versions#sql-server-service-broker-ssb
- Support and development of Microsoft and Nintex based applications
- Application design and development including digital processes
- Invoice management
- Requisition management
- Contract management
- Modern Intranet
ISCG sp. z o.o.
Al. Jerozolimskie 178, 02-486 Warsaw
NIP: 5262798378
KRS: 0000220621
Phone