OpsMgr Support Tip: Email notification may not work as expected if a time range is configured only with an exclusion

OpsMgr Support Tip: Email notification may not work as expected if a time range is configured only with an exclusion

  • Comments 2
  • Likes

Tools_thumb2Vasanth Kumar | Support Engineer

Hey there again! This is Vasanth from the Operations Manager team and today I have a quick tip for you all that I found while working on a recent issue.

When using Systems Center Operations Manager (any version of OpsMgr 2007 or OpsMgr 2012), if you configure Notification Recipients (so called up to OpsMgr 2007 SP1) or Subscribers (as called in OpsMgr 2007 R2 and OpsMgr 2012) with the option of "Only send notification during the specified times" and you configure it with only an exclude range (like "Except from" with a time range of, say 1:00am to 7:00am for example), email notifications fail altogether.

In the Operations Manager event log you will also see the event below:

Log Name:      Operations Manager
Source:        Health Service Modules
Date:          <date> <time>
Event ID:      31501
Task Category: Notification
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      <RMS Server Name>
Description:
No primary recipients were specified for the notification or all recipients are unavailable according to the schedules. Notification will not be sent

One or more workflows were affected by this. 

Workflow name: Subscription431bd31a_37fc_4375_9cd7_29bb8a11c600
Instance name: Alert Notification Subscription Server
Instance ID: {E07E3FAB-53BC-BC14-1634-5A6E949F9230}
Management group: <Mgmt Group Name>

So what’s going on? Since we configured it to send only during specified times and then only included an excluded range, the system does not recognize any valid time that emails can be sent so it never sends any.

So to keep this from happening, or to fix it if you’ve already found yourself in this situation, you need to configure the Recipient or Subscriber first with an included time range, then configure your excluded time range.

For example, first configure you include Range like Date  | Range = Always | Time Range = All Day | Weekdays = Week days. then once you have that, configure your Exclude Range like Data Range = Always | Time Range = Excluding 1:00am to 7:00am | Weekdays = Week Days. The screen shot below shows this configuration.

 

I hope this helps!

Vasanth Kumar | Support Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • or you can configure two schedules that have the gap you want: if you want to exclude 4am to 5am, configure one schedule from 00:00 to 3:59, and another from 5:01 to 23:59.

    I don't think I've ever noticed that event in the logs before. I usually apply the schedules to individual addresses within the recipient, rather than on the recipient itself. would the behavior/event be the same in that case?

  • can't see the picture in the end of post :(