Skip to content
English
Submit a support ticket
Back to www.opslogix.com
  • There are no suggestions because the search field is empty.

Check Connection or Refresh on the Assign tab never finishes

Fix the SQL Service Broker settings when dashboard tasks hang and never finish.

Applies to: OpsLogix VMware and Oracle Management Packs (all versions) · SCOM 2019, 2022, 2025
Last updated: October 2026 · Reading time: 4 minutes

Symptom

In the VMware or Oracle MP configuration dashboard, Check Connection or Refresh on the Assign tab keeps running and never finishes. You can't add a connection or assign host sockets.

Cause

The dashboards use SCOM tasks to check connections and to load and save license assignments. SCOM tasks rely on the SQL Server Service Broker together with the SCOM SDK service. If the Service Broker isn't configured correctly on the OperationsManager database, the tasks never return a result.

Resolution

First check the task status. Check Connection first installs or updates the collector on every server in the resource pool and then tests the connection. Each part can take up to 5 minutes, so wait at least 10 minutes. Then open Monitoring > Task Status in the Operations console and look at the OpsLogix tasks:

  • Scheduled and nothing happens: the SCOM SDK or the SQL Server Service Broker doesn't pass the task on. Continue with the steps below.
  • Started for a long time: the Microsoft Monitoring Agent on that server is busy or stuck. Check the agent on the server named in the task.
  • Failed: open the task output. It shows the error.

The examples use the default database name OperationsManager. Change it if your database has a different name. Run the queries as a SQL administrator in SQL Server Management Studio.

Step 1: Make sure the Service Broker is enabled

Check whether the Service Broker is enabled:

USE [master]
GO
SELECT is_broker_enabled FROM sys.databases WHERE name = 'OperationsManager';

The result should be:

is_broker_enabled
-----------------
1

If it's 0, enable the Service Broker:

USE [master]
GO
ALTER DATABASE OperationsManager SET ENABLE_BROKER WITH ROLLBACK IMMEDIATE;

Then restart the System Center Data Access Service on all SCOM management servers, so the SCOM SDK recreates its task queue:

Restart-Service 'OMSDK'

Step 2: Make sure the database has an owner

The owner should be sa (the default) or a domain account. Check the owner:

USE [master]
GO
SELECT suser_sname( owner_sid ) as 'owner' , name as 'database'
FROM sys.databases
where name = 'OperationsManager'

The result should look like this:

owner                  database
---------------------  ------------------------
sa                     OperationsManager

or, with a domain account:

owner                  database
---------------------  ------------------------
CONTOSO\scom_DB_owner  OperationsManager

If no owner is set, set it to sa:

ALTER AUTHORIZATION ON DATABASE::[OperationsManager] TO [sa];

or to a domain account (change the login name if needed):

ALTER AUTHORIZATION ON DATABASE::[OperationsManager] TO [contoso\scom_DB_owner];

Then restart the System Center Data Access Service on all SCOM management servers:

Restart-Service 'OMSDK'

Verify it worked

Open the configuration dashboard again and click Check Connection or Refresh. It should now finish and show a result.

See also