SCOM 2019 Alert notifications error - Failed to send notification

Question

Hello All,

Could someone please help me with below issue ?

We have often received Failed to send notification (SCOM-2019) alert in Production environment.

We have checked the all the possibilities and SMTP server connection and logs all are ok.

Its failing for different account and mainly happen in Prod environment. Our Non-Prod env is working fine.

We have 3 Management servers and all are added into resource pool notification.

Here the Notification is happening only in our 3rd Management server not rest of 2 MS servers.

Please advise.

Thanks,

Adam

Answer 1

Hi,

This issue could be caused by a variety of factors. One potential cause could be that the alert notifications are not meeting the defined criteria for the recipients' subscriptions or that notification is configured incorrectly. Another potential cause could be that the SMTP server's address or port is blocked by firewall rules or anti-malware software, which can prevent the notifications from being sent.

Since you have checked the SMTP server connection and logs, it is possible that the issue is related to the recipients' subscriptions or notification configuration. You may want to review the notification settings to ensure that they are configured correctly and that the recipients have subscriptions that match the criteria for the alerts.

If the issue persists, you may want to review the firewall rules and anti-malware software settings to ensure that they are not blocking the notification traffic. You can also try creating exclusions for the resource pool servers in the firewall rules and anti-malware software settings, as mentioned in the Microsoft documentation.

Lastly, you may want to review the event logs on the management servers to see if there are any error messages or warnings related to the failed alert notifications. This may provide additional information about the cause of the issue.

Answer 2

we are also using SCOM2019 with one management-server and have exact the same problems! i assume it has something to do with the installation of the last cumuluative windows updates from june (before we didnt have any problems and there was no configuration change or something like that)

Answer 3

Having the same issue and it's happening intermittently, alerting is working for the defined subscription however sometimes this error pops up, in terms of SMTP and criteria I'm pretty sure they are set correctly as we are getting email alerts

Answer 4

final status from my side:

we had opened a microsoft case to analyze the root cause. in our case it was the default timeout-value for the receive-connectors on our exchange relay-server (10 minutes) -> we received a MS tool to collect exchange logs and sent the logs afterwards to the MS engineer. and he saw that the affected messages runned into a timeout (10 minutes and some seconds) and could not send because of the default timeout-value of 10 minutes.

we set the following commands in our exchange management shell of the exchange relay server:

o Set-ReceiveConnector -Identity “[hostname][receiver connector]” -ConnectionTimeout 00:20:00

o Set-ReceiveConnector -Identity “[hostname][receive connector]” -ConnectionTimeout 00:20:00

since then we have no more problems with sending e-mails from our SCOM environment.