{"id":202,"date":"2009-10-08T09:47:13","date_gmt":"2009-10-08T15:47:13","guid":{"rendered":"http:\/\/www.briandeyo.us\/brd\/wp\/?p=202"},"modified":"2009-10-08T09:52:04","modified_gmt":"2009-10-08T15:52:04","slug":"operations-manager-not-sending-email-after-im-notification-settings-changed-event-id-4509","status":"publish","type":"post","link":"https:\/\/www.briandeyo.us\/index.php\/2009\/10\/08\/operations-manager-not-sending-email-after-im-notification-settings-changed-event-id-4509\/","title":{"rendered":"Operations Manager not sending email after IM notification settings changed. Event ID 4509."},"content":{"rendered":"

For several hours I’ve been trying to retrace my steps on how\u00a0I managed to break our\u00a0Operations manager 2007 email notifications.\u00a0 For 2 days now alerts are being triggered and our server’s health states are being updated, but no email was getting out.<\/span><\/p>\n

I checked the message tracking logs on Exchange and nothing was ever leaving the OpsMgr<\/span> server.\u00a0 I tried to telnet to the smtp server and that worked.\u00a0 I checked the logs and there was an innocuous message about the “Instant Notification” settings I were using, and how it was causing a notification workflow<\/span>.\u00a0 The app log message looked like this:<\/span><\/p>\n

\n

Event Type: Error
\nEvent Source: HealthService<\/span><\/span>
\nEvent Category: Health Service
\nEvent ID: 4509
\nDate: 10\/8\/2009
\nTime: 9:38:07 AM
\nUser: N\/A
\nComputer: OPS-RMS
\nDescription:
\nThe constructor<\/span> for the managed module type “Microsoft.EnterpriseManagement<\/span>.HealthService<\/span>.Modules.Notification.Sip.SipNotificationTransportModule<\/span>” threw an exception. This module was running in rule “Subscriptiond2e36701_7544_4b03_9c18_811f5d34a5fd<\/span>” running for instance “Alert Notification Subscription Server” with id:”{E07E3FAB-53BC-BC14-1634-5A6E949F9230}” in management group “GROUP”.<\/span><\/p>\n

\u00a0<\/p>\n

The exception text is:
\nMicrosoft.EnterpriseManagement<\/span>.HealthService<\/span>.ModuleException<\/span>: The specified Uri : (sip:email<\/span>@im.vanity.com\/home) has one or more invalid elements. A valid sip uri<\/span> should be of the format sip:user@host.<\/span>
\nParameter name: uri<\/span> —> System.ArgumentException<\/span>: The specified Uri : (sip:email<\/span>@im.vanity.com\/home) has one or more invalid elements. A valid sip uri<\/span> should be of the format sip:user@host.<\/span>
\n\u00a0<\/span><\/p>\n

(insert lenghty description of lots of things going crunch)<\/span><\/p>\n

For more information, see Help and Support Center at http:\/\/go.microsoft.com\/fwlink\/events.asp.<\/p>\n

\n

\u00a0<\/p>\n

So I decided it was important to revisit my IM settings, since I knew that was what I was working on the day notifications had stopped. And there it was glaring at me in the face. the last thing I changed was added “\/home” to the “Return Address” under the notification settings.<\/p>\n

Once I removed that I proceeded to get 2 days worth of back-logged alerts. It is interesting to note that an error with the IM notification workflow<\/span> actually affected the Email notification also. <\/span><\/p>\n

I’m just happy I found it and fixed it. In case anyone ever sees the Event ID 4509 on your RMS, I would suggest visiting your notification settings.<\/p>\n","protected":false},"excerpt":{"rendered":"

forward-slash in IM ‘return address’ field for OpsMgr notification breaks all notification workflows<\/p>\n","protected":false},"author":12,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[24,41,40,23,39],"class_list":["post-202","post","type-post","status-publish","format-standard","hentry","category-tech","tag-email","tag-im","tag-instant-message","tag-operations-manager","tag-opsmgr"],"_links":{"self":[{"href":"https:\/\/www.briandeyo.us\/index.php\/wp-json\/wp\/v2\/posts\/202","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.briandeyo.us\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.briandeyo.us\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.briandeyo.us\/index.php\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.briandeyo.us\/index.php\/wp-json\/wp\/v2\/comments?post=202"}],"version-history":[{"count":4,"href":"https:\/\/www.briandeyo.us\/index.php\/wp-json\/wp\/v2\/posts\/202\/revisions"}],"predecessor-version":[{"id":205,"href":"https:\/\/www.briandeyo.us\/index.php\/wp-json\/wp\/v2\/posts\/202\/revisions\/205"}],"wp:attachment":[{"href":"https:\/\/www.briandeyo.us\/index.php\/wp-json\/wp\/v2\/media?parent=202"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.briandeyo.us\/index.php\/wp-json\/wp\/v2\/categories?post=202"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.briandeyo.us\/index.php\/wp-json\/wp\/v2\/tags?post=202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}