Make sure the Enhanced Notification Service for SCOM (ENS for SCOM) and the System Center Data Access Service (OMSDK) is started on ALL notification servers.


Open the SCOM Operations manager console and generate an alert notification for the notification channel you have created. If you have an All Alerts channel setup, close or open an alert and it will be sent to the Enhanced Notification Service for SCOM.


If you are having issues check the application event log on the server where ENS for SCOM is installed (or all notification servers in the notification server resource pool).  


The workflow for the service is:


  1. The service receives the alert from SCOM via SMTP.   Check the SCOM console for Failed to send notification or Failed to send notification using server/device.  These alerts in the console mean that SCOM was unable to deliver emails to ENS for SCOM.  Check host names and port in the Notification channel.  Check firewall settings for port 25 inbound to the machine where ENS for SCOM is installed.  If this is working you will see event id 2. (below)
  2. Communication to the SDK Service. ENS for SCOM looks up information about the alert and attempts to send the email downstream.  If this is not working check to see if firewall ports are open for tcp 5723, 5724 to the machine where the OpsMgr SDK service is running.  Check service ENS for SCOM is running under and login to the machine having issues with the service account.  Check to see if service account is local admin as well as a Operations Manager Administrator.  If this is working you will see event id 3 (below).
  3. ENS for SCOM delivers the notification to the downstream SMTP messaging environment.   If you are seeing event id 2 Exception caught or event id 3 timeouts, then check outbound ManagementServer1-4, smtpserver, smtpport, smtpuser/smtppassword for destination SMTP server (smtpserver) in the EnhancedNotificationService.exe.confg, check firewall settings for port 25 or 465 outbound. If this is working you will see event id 10 (below)


Success Event Alert ID in order


Event ID 2

SMTP In - New Alert Received. Connecting IP: 127.0.0.1

From: <from email address>

To: <notification email address>

This event shows processing of Management Pack knowledge (if any)


Event ID 3

Processing: C:\<install path>\queue\<guid>.txt

Attempt 0 of 100

This event shows delivery to the messaging environment and to the users email.


Event ID 10

mailClient.Send(From: <from email address> To: <notification email address> )

Alert Id: <guid>

<description of the alert>

Attempt: 0 of 100

SMTP host: <SMTP server>:25

Sent - OK


Troubleshooting

For troubleshooting, you should check the application event log on the machine for Informational and error event log entries for ENS for SCOM.


Informational Event log messages and ID’s


Event ID 1 – Service Starting


Event ID 1 – Service Stopping


Event ID 2 – SMTP in: envelope From: {0} Envelope To: {1}


Event ID 3 – Processing: <notification file> attempt <int attempt> of <maximumProcessRetries>


Event ID 10 – Notification Delivered to external SMTP Server OK


Error Event log messages and ID’s


Event ID 1 – Cannot connect to SCOM Management Server: <ManagementServer> <err msg>


Event ID 1 – No AlertID was found, please send notifications to this service with the SCOM Alert Id in the Subject of the email.


Event ID 2 – Exception caught in SendEmailMessage(From: <from> To: <to> ) and error why.


Event ID 3 – Error processing: <notification> Maximum retry hit: <attempts> out of <maximumProcessRetries>