Test/Troubleshooting your install

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).  

How the service works:

  1. The service receives the alert from SCOM via SMTP.   If this is working you will see event id 2.

    Check the SCOM console for     Failed to send notification or Failed to send notification using server/device alerts.
    If you see one of these, SCOM was unable to deliver emails to our service.  

    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. 

  2. The service attempts to contact the SCOM OMSDK service to look up information for the alert it just received. If this is working you will see event id 3 in the application event log.

    If this is not working check the application event log for errors. (See table below)

    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.  

  3. ENS for SCOM delivers the notification to the downstream SMTP messaging environment. 

    If this is working you will see event id 10 in the application event log.

    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.

Successful processing of a notification in order

Each notification received will generate 3 event log entries. You will see:

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>