Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DBADave
Constraint Violating Yak Guru
366 Posts |
 Posted - 2004-03-22 : 15:39:19
|
| I defined an Alert in Enterprise Manager for Severity 19 - Fatal Error In Resource. The alert is enabled, the type is "sql server event alert" and the alert is defined against a specific database. SQLSERVERAGENT and SQL Mail session are both started. I test the alert using the following statement in the specified database.raiserror (50001,19,1) with logA message is placed in the SQL Server log, however no alert is fired. The alert history indicates the alert has never occurred. What am I missing?Thanks, Dave |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-22 : 15:51:16
|
| I just tried exactly what you said and it works for me. Is the alert enabled? Did you refresh EM? I had it send me a message using NET SEND as I don't have SQL Mail configured on the server that I configured the alert on. I didn't get the NET SEND message though but the alert did fire as seen in EM. I got it when I tested it through the creation of the alert but not when the alert fired, not sure why.Tara |
 |
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2004-03-22 : 16:00:32
|
| In EM where the Alerts are listed this particular alert has YES in the Enabled column and 19 in the Severity column, however Last Occured indicates (Never Occurred). Everything looks ok, but something has to be missing. I tried this on multiple servers without success. My EM connection is either using SA or Windows Authentication. In the cases with Windows Authentication my id has local admin rights on the server. I know I'm missing something simple, but according to the steps in BOL the process is simple.Dave |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-22 : 16:02:53
|
| Did you refresh the alerts screen though in EM? I had to refresh it in order to see that the alert fired. If it still shows that it has never occurred, is the SQLSERVERAGENT service started?Tara |
|
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2004-03-22 : 16:13:37
|
| I refreshed EM earlier and still saw no history. This time I disconnected and reconnected the instance. For some reason I have to do this in certain situations. After reconnecting I noticed a history existed under a demo for Severity 19. I didn't realize the demos were enabled. I just disabled the demo alert and all appears to be working.Thanks, Dave |
|
|
|
|
|
|
Problem Triggering Alerts