pch

OK, in reading the response above you are saying SQL instead of DQL (my email came across as DQL, sorry). I went to the database and checked the alerthistory table and everything is dated for December 21 of last year. I checked a few other alert tables and didn't find anything conclusive.

Hi, not sure what you mean by “dql”. Can you please elaborate? Also, are you referring to a sql table when you mention orion.alerthistory table? Just want to make sure I am clear on what you are saying. Is this what you are referring to when you mention the error in the message column? My other email alerts are working so…

I wanted to let you know that my colleague found out what the issue was. He needed to go into IIS (8.5) and enable forms authentication. That resolved it.

No we just have the one server. We believe the problem is the login.aspx form in a server 2012 R2 environment. That form doesn’t work for anyone. You can go to the site, look at reports, export them to PDFs just fine, but if you save them as PDFs in the scheduler, it gets hung up at the login and that is what gets returned…

OK, it looks like it is working correctly SOMETIMES!!!!! The alert always goes out but not the email. Sometimes it goes out and sometimes it doesn't. Any ideas?

OK, I found out that the return address I was using (default) on the mail alerts made it look like it was coming from outside the environment and our Exchange 2010 defaults to requiring authenticated users to send to a distribution group. These were new distribution groups that we were sending to, so they defaulted to that…

OK, so almost a week after I set this up, it just suddenly started working correctly. The mails went out when the alerts got entered into the NPM event logs. No changes were made, no reboots were done, nothing. It just started working.

No, we aren’t requiring https.

I spoke too soon. I removed my name and added the distribution group and now it is not working again. I have done distribution groups before so it shouldn't be that.

Other email alerts are working. No AV issues.

I agree, the variable shouldn't prevent the email from going out. The preview of the email looks good. The alert to the NPM triggers but the email never does. I have those two actions in the alert. I actually copied this from another alert that is working properly, making an entry in the NPM alert and sending out an email…

Thanks for the info. It was VERY helpful. Unfortunately I have run into a bit of a quandary and was wondering if you could help further. I followed your recommendations and chose from the MSExchange Transport Queues for the Performance Object in the wizard. First I went with the Aggregate Delivery Queue Length (all…

Sorry to bug you again, but I have one more thing. I went through and cleaned up the settings on the maps like you showed below and I have a handful of placeholders on the limited view. There is no consistency (e.g. nested map), it is just a few with my testing so far, but you open it up and it has the title of the map and…

I found it. I had to open the maps first. That did the trick. I did find that since we have a bunch of nested maps, I had to go to the nested maps as well to remove any traces. Otherwise I would end up with grey placeholders. Thanks again. This really helped a lot. : )

I didn’t see that option. Is that in the network atlas itself? I didn’t see anything like that when looking previously, but maybe I just missed it. If that option is available this would be awesome!

I think I figured it out. I changed the email from plain text to html and the emails landed in my inbox.