The SQL Server Service Broker for the current Opsmgr database is not enabled
Yesterday I came accros this error:
Saying that the SQL server Service Broker or database mirroring endpoint is disabled or not configured.
![clip_image002[4] clip_image002[4]](http://scug.be/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/scom/clip_5F00_image002_5B00_4_5D005F00_thumb_5F00_6F23CC0D.jpg)
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:
- First stop the opsmgr SDK service
- Open SQL Server Management Studio.
- Click New Query
- In the query window, enter the following query: ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE
- Click Execute.
- Click New Query
- Enter the following query: ALTER DATABASE OperationsManager SET ENABLE_BROKER
- Click Execute.
- Click New Query.
- In the query window, enter the following query: ALTER DATABASE OperationsManager SET MULTI_USER
- Click Execute.
- 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'.
- Restart your Opsmgr SDK service.
That’s it!
Grtz,
Alexandre Verkinderen
http://scug.be/blogs