How to resolve SCOM Notifications Stopped & No New Alerts

Posted by : at

Category : troubleshooting   operationsManager


First thing I noticed was that the SCOM Management Servers had an SCOM Agent Installed on it. We verifing by navigating to the following location, you can see the Agent Management Groups: Management Server - Bad Registry Keys

Apparently the Operations Manager Management Server received a package from SCCM, and this attempted to automatically install the SCOM Agent (Microsoft Monitoring Agent). And during this process the installer overwrote some registry keys inside of the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\

Precaution

Take care when directly modifying the Registry via regedit.exe. If you insist on making changes, always backup the registry first. There is always the possibility you can cause more damage than you are fixing.

I had the customer Delete the Agent Management Groups key and we matched / created the Registry Values for Server Management Groups compared to my lab environment. We needed to create the Management Group Name Key in my situation. Management Server - Good Registry Keys

After doing this we cleared the cache on the SCOM Management Servers by running the following PowerShell script:
SCOM-Scripts-and-SQL/Clear-SCOMCache.ps1 at master · blakedrumm/SCOM-Script-and-SQL

We waited for a few minutes after clearing the SCOM Management Server cache. The Management Servers were coming back online, but they were still not receiving new Alerts, and there were not any Notification Emails.

While reviewing the Operations Manager Event Logs, we found that there were 2115 Errors indicating an issue with the insertion of Discovery and other related data:


Event 1

Log Name: Operations Manager
Source: HealthService
Date: 1/20/2022 3:42:02 PM
Event ID: 2115
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: ManagementServer1.contoso.com
Description:
A Bind Data Source in Management Group ManagementGroup1 has posted items to the workflow, but has not received a response in 480 seconds. This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectEventData
Instance : ManagementServer1.contoso.com
Instance Id : {AEC38E5Z-67A9-0406-20DB-ACC33BB9C4A4}


Event 2

Log Name: Operations Manager
Source: HealthService
Date: 1/20/2022 3:42:02 PM
Event ID: 2115
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: ManagementServer1.contoso.com
Description:
A Bind Data Source in Management Group ManagementGroup1 has posted items to the workflow, but has not received a response in 480 seconds. This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectPerformanceData
Instance : ManagementServer1.contoso.com
Instance Id : {AEC38E5Z-67A9-0406-20DB-ACC33BB9C4A4}


Event 3

Log Name: Operations Manager
Source: HealthService
Date: 1/20/2022 3:42:02 PM
Event ID: 2115
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: ManagementServer1.contoso.com
Description:
A Bind Data Source in Management Group ManagementGroup1 has posted items to the workflow, but has not received a response in 480 seconds. This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectPublishedEntityState
Instance : ManagementServer1.contoso.com
Instance Id : {AEC38E5Z-67A9-0406-20DB-ACC33BB9C4A4}


Event 4

Log Name: Operations Manager
Source: HealthService
Date: 1/20/2022 3:42:03 PM
Event ID: 2115
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: ManagementServer1.contoso.com
Description:
A Bind Data Source in Management Group ManagementGroup1 has posted items to the workflow, but has not received a response in 480 seconds. This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectSignatureData
Instance : ManagementServer1.contoso.com
Instance Id : {AEC38E5Z-67A9-0406-20DB-ACC33BB9C4A4}


Event 5

Log Name: Operations Manager
Source: HealthService
Date: 1/20/2022 3:42:30 PM
Event ID: 2115
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: ManagementServer1.contoso.com
Description:
A Bind Data Source in Management Group ManagementGroup1 has posted items to the workflow, but has not received a response in 480 seconds. This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectDiscoveryData
Instance : ManagementServer1.contoso.com
Instance Id : {AEC38E5Z-67A9-0406-20DB-ACC33BB9C4A4}


We reviewed the current SQL Logs and found that there were authentication failures that indicated the Computer Account for the SCOM Management Server didnt have permission to the Database. This lead us to check the Default Action Account in Run As Profiles. We modified the Default Action Account for the Management Servers to be assigned an Windows Action Account instead of Local System. This resolved the issue and now Notifications and Alerts are being being sent normally.

Page Views


Share on:
About Blake Drumm
Blake Drumm

I like to collaborate and work on projects. My skills with Powershell allow me to quickly develop automated solutions to suite my customers, and my own needs.

Email : [email protected]

Website : https://blakedrumm.com

About Blake Drumm

This is the personal technical blog for Blake Drumm. Currently primarily focused towards Microsoft System Center Enterprise Management Products. I am an Microsoft Support Engineer on the System Center North America Support Team. I am new to blogging. July 6th, 2021 marks my first day as a Microsoft FTE converting from a contractor. I had been working as a contractor since January 2020. Continue to check back for new posts or tips. I like to continually update this page as time permits.

Follow @blakedrumm
Useful Links