Matthew Darwin (3/27/2014)
I tried this, but no definitely nothing to do with the log shipping configuration. It seems far more to be to do with alerts in general; I know this because I've set up a different alert on a custom error message, configured that to notify an operator, run a RAISERROR calling the alert and seeing that be sent to the SQL Server Error log but no alert fired.So log shipping is a red herring; it's entirely to do with SQL Server not firing alerts when it should.
Any thoughts on where to look to resolve this?
First check this ..
Also check if the Operator is enabled or not. Rt click on alert and see if Enabled CheckBox is checked. And in the Notifications tab check for the option "View Notifications sent to this user by " , Alerts has been selected.
And for the Alert, check if "Notify Operators" has been checked and the Operator has been selected with Email option.
Also check if your Failsafe Operator has been enabled in the SQL Server Agent properties.
If the above is all good then ..
Start SQL Profiler and try to trigger an alert using RAISERROR and check if anything gets captured in the profiler trace. Also check the SQL Error Log, Windows Application & System logs for any message around this time.
--
SQLBuddy