The SQL Server Service Broker for the current Opsmgr database is not enabled

1 minute read

Yesterday I came accros this error:

image

Saying that the SQL server Service Broker or database mirroring endpoint is disabled or not configured.

clip_image002[4]

If you don’t know what the SQL server service broker exactly is, have a look here: An introduction to SQL server service broker. In summary the Service Broker, internal or external processes can send and receive guaranteed, asynchronous messaging by using extensions to Transact-SQL. And it needs to be up and running for our Opsmgr DB.

So I did a search on google and found this post where they describe how to enable the service broker.

 

In summary:

  1. First stop the opsmgr SDK service
  2. Open SQL Server Management Studio.
  3. Click New Query
  4. In the query window, enter the following query: ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE
  5. Click Execute.

  6. Click New Query
  7. Enter the following query: ALTER DATABASE OperationsManager SET ENABLE_BROKER
  8. Click Execute.
  9. image

  10. Click New Query.
  11. In the query window, enter the following query: ALTER DATABASE OperationsManager SET MULTI_USER
  12. Click Execute.
  13. image

  14. You can verify the setting for ENABLE_BROKER is set to 1 by using this SQL query: SELECT is_broker_enabled FROM sys.databases WHERE name=’OperationsManager’.
  15. Restart your Opsmgr SDK service.

 

That’s it!

 

Grtz,

Alexandre Verkinderen

http://scug.be/blogs

 

 

 

Leave a comment