SCSM Workflows stuck and Connectors do not sync

In a customer environment we had the problem that Workflows in System Center Service Manager suddenly stopped running. Service Request stuck in status “new” and the Connectors stopped working.

There are several posts in the internet with a common method to fix this: Stop System Center Services, clear the cache folder and start the services again.
This did not help here!

Even enabling SQL Broker did not help.

What I know now is, that one MonitoringHost.exe process should run with the SCSM Workflow Account, see later in this post.

The common and likely for the most cases working solution is:

  1. Stop the 3 System Center Management services on the Service Manager Management Server responsible for your workflows:
    • Microsoft Monitoring Agent
    • System Center Data Access Service
    • System Center Management Configuration
  2. Delete the contents of the C:\Program Files\Microsoft System Center 2012\Service Manager\Health Service State folder.
  3. Restart the 3 services listed above.

The issue in our case was not to solve with this method. So, we called Microsoft Support. Thanks again for your great support, Omar!

He noticed that in Task Manager of the Service Manager Workflow Server (Management Sever) no MonitoringHost.exe process is running with the Workflow Account.

Further research shows that the Regkeys for the SCSM Management Group in
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Server Management Groups]

and [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Management Groups] were missing.

Creating the keys again solved the problem. In our case we get them from HKEY_LOCAL_MACHINE\CurrentControlSet001.

After importing the reg keys and restarting the service Microsoft Monitoring Agent in Task Manager we saw that one MonitoringHost.exe process was running with the Workflow Account. And …the Service Manager workflows run 😊.

SQL Broker is not needed for this but it should be enabled If the SQL broker service is running then the consoles will update with new/changed MP content without a close/reopen.
But SQL Brokeris not needed for SCSM workflows.


Starten Sie jetzt Ihren Weg zu Azure!

Los geht's