https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMTQ3IiwiaGFzaCI6IjFiYmE4NWFiLTU5ODQtNDFmNi1hZDNhLTUyZDgxYjBjODU0MSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Alerts are not closed automatically in SCOM

Challenge

Alerts are not closed automatically in SCOM.

Cause

This behavior can be seen in one of the following scenarios:
 

  • The closing event does not arrive.
  • The event that would normally close the alert arrives so quickly after the error event that both share the same time stamp.

Solution

The first thing to check is that the closing event arrives and is logged in the nworks collector event log.

If the event is there, and matches the alert generating event, it is a good idea to pay attention to the time stamp. If both the alert generating event and the alert closing event arrive so quickly that they have the same time stamp in the event log, this is an issue with SCOM.

In SCOM SP1, it is a known issue that if the alert generating event and alert closing event have the same time stamp, the alert may not be closed automatically. There is no other option but to close it manually in this case.

More information

As per information from Microsoft, in SCOM R2, the situation is somewhat better; however, there is still no way to ensure that the alert will be closed automatically in the scenario described.

KB ID:
1147
Product:
Veeam Management Pack for Microsoft System Center
Version:
5.x
Published:
2011-08-05
Last Modified:
2020-08-28
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later