Skip to main content

adjusting “failed to send notification using server/device”

the actual rule name is “Failed to send through device alerting rule” that we’ll be working with.  i’m not going to go into length explanations since this is fairly straightforward.  just a few things that i wanted to point out (mainly links to good info).  basically, this alert has no overrides that are useful.  it kept sending out messages that looked like this:

Notification subsystem failed to send notification using device/server ‘' over 'sip' protocol to ''. Microsoft.Collaboration.SignalingException: The requested operation failed.: Sip response: Temporarily Unavailable (0x1e0). Rule id: Subscriptione94d0bc3_ff32_48dc_8e96_3fdda0ba1663

this tends to come up often if the user is not online when the alert is sent through.  i suppose you could try to limit the number of times you’d run into this scenario by adjusting the hours that IM is used for alert notification (or not using it at all).  i opted to create an identical rule with the right event criteria.

  • ran logparser and dumped the event so that i could see the exact parameters.  it’s detailed HERE on stranger’s blog.  the output is separated by pipes.  i reformatted it to make it easier to read:
1 myManagementGroup|
2 Subscriptione94d0bc3_ff32_48dc_8e96_3fdda0ba1663|
3 Alert Notification Subscription Server|
4 {E07E3FAB-53BC-BC14-1634-5A6E949F9230}|
5 sip|
8 Microsoft.Collaboration.SignalingException|
9 The requested operation failed.: Sip response: Temporarily Unavailable (0x1e0)

  • created an identical rule with the following properties (reference HERE for kevin’s blog post if you need more information):
    • expression -
      • Event ID equals 31503
      • Event Source equals Health Service Modules
      • Parameter 1 equals $Target/ManagementGroup/Name$
      • Parameter 5 does not equal sip
    • response -
      • Suppression – Parameter 5, 6, 7, 8, 9

now you simply need to disable the original rule and turn this one on (saving it to your own management pack of course).  we simply set the event rule to pick up where parameter 5 does not equal sip.  by doing this we’ve effectively stopped any alerts on notifications where sip is involved.


Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …