SELECT CONVERSATION_HANDLE, service_id, far_serviceįETCH NEXT FROM conv_cur INTO = 0 and (select top 1 s.name from sys.service_queues as q join sys.services as s on q.object_id=s.service_queue_id WHERE q.name like order by q.create_date asc) Run the following SQL queries in order: declare int Go to the next step to re-create the SQL Server Service Broker. If you still can't find the queue and service, the current Service Broker may be corrupted. If you can't find the corresponding queue and service, restart the OMSDK service again. If you have more than one management server, each management server will have a separate Service Broker queue and service. In this example, the IP address of the management server is 192.168.10.10.

The process ID of the OMSDK service (.exe) that's running on that management server.

The IP address of the management server that created the queue and service.

Verify that there's a queue and service whose name contains the following values: In SQL Server Management Studio, go to Databases > OperationsManager > Service Broker. Restart System Center Data Access ServiceĪfter SQL Server Service Broker is enabled, restart System Center Data Access Service (OMSDK). Otherwise, run the following SQL queries to enable it: ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATEĪLTER DATABASE OperationsManager SET ENABLE_BROKERĪLTER DATABASE OperationsManager SET MULTI_USER

If the returned value of the is_broker_enabled field is 1 (one), SQL Server Service Broker is enabled. Run the following SQL query: SELECT is_broker_enabled FROM sys.databases WHERE name = 'OperationsManager' Check whether SQL Server Service Broker is enabled Replace OperationsManager with the name of your operational database if you use a different database name. The SQL queries in this article use a default name of OperationsManager for the operational database.

Stale queue meaning