Configuration monitor indicates a problem with configuration of the Notification subsystem. The notification configuration may be a corrupted state or is unable to read it from the corrupted state.

Notification subsystem was unable to retrieve the state because of database errors. The state is being set from the module configuration. You may see duplicate notifications. Another problem could be that Notification subsystem was not able to read the state information. Notification subsystem was unable to read time zone information and reverted to UTC.

Notification subsystem is unable to generate notification messages due to configuration problems. This may be due to one of many reasons.

• Check if the subscription information has been set correctly.

• Check to make sure your Operations Manager and especially the Notification subsystem is configured correctly.

• Inspect the messages in the Operations Manager event log. Other indications of problems in the system may direct you to further diagnostic steps. There may be other failures in the OpsMgr runtime.

• The subscription might be missing timezone information. The Notification subsystem has reverted back to using UTC for displaying time sensitive fields in the notification messages.

• Backup and recreate your subscriptions for OpsMgr.