Comments
Sort by recent activity
Daniel,
have just emailed you.
Kev / comments
Daniel,
have just emailed you.
Kev
Daniel,
Reason for not starting: Reasons unknown
All servers are on the same timezone
Kev / comments
Daniel,
Reason for not starting: Reasons unknown
All servers are on the same timezone
Kev
Daniel,
there seems to be no pattern. It is affecting different jobs at different times on different servers.
Kev / comments
Daniel,
there seems to be no pattern. It is affecting different jobs at different times on different servers.
Kev
Daniel,
schedule is "Occurs every day every 12 minute(s) between 00:10:00 and 23:40:00"
Kev / comments
Daniel,
schedule is "Occurs every day every 12 minute(s) between 00:10:00 and 23:40:00"
Kev
Brian,
thanks for the response. I have rechecked one of the alerts Previous execution of this job was overrunning - No - in fact the previous run had also finished with 0 duration, but that hadn't fired an alert SQL Server Agent was not running (a SQL Server Agent not running alert is raised when SQL Response first detects that SQL Server Agent is not running) - No - agent was certainly running No target servers defined - No, the target is set to 'local server'
It is strange that other runs of the same job that have 0 duration are not triggering the alert - so I guess it isn't strictly a 0 duration issue. Could it be that SQL Response is doing a dirty read on the MSDB database?
Kev / comments
Brian,
thanks for the response. I have rechecked one of the alertsPrevious execution of this job was overrunning - No - in fact the previous run had also finished with 0 duration, but that hadn't ...
Emma,
yes that's it!!
I cleared all outstanding alerts, and now my inbox is filling nicely!
I am getting it for new, first time alerts but not for subsequent. I believe that this is by design.
If I clear the alert, I do get the email the next time.
That will teach me to clear the alerts down properly, and not just let them expire from the current view.
Thanks,
Kev / comments
Emma,
yes that's it!!
I cleared all outstanding alerts, and now my inbox is filling nicely!
I am getting it for new, first time alerts but not for subsequent. I believe that this is by design.
If I...
Emma,
strangely enough, I have come into the office this morning to see 1 alert email in my inbox. There have been over 50 alerts triggered overnight, but only 1 email.
In the AlertRepositoryLogFile.Log
there is a line
00:59:46.306|Info |AlertRepository |4 |Mail sent OK
Don't know if this helps or hinders the issue?
Kev / comments
Emma,
strangely enough, I have come into the office this morning to see 1 alert email in my inbox. There have been over 50 alerts triggered overnight, but only 1 email.
In the AlertRepositoryLogFi...
Emma, thanks for the response.
Did you fail to receive an email notification for an alert that was raised within the GUI? Yes
Is this issue present for all server instances that you are connected to? Yes
If you go to the Configure a server tab of the configuration dialog and navigate to the appropriate Job alerts for the server concerned
Is the email address correctly listed in the Send email to text box? Yes
Are the alerts enabled? Yes / comments
Emma, thanks for the response.
Did you fail to receive an email notification for an alert that was raised within the GUI? Yes
Is this issue present for all server instances that you are connected t...
I seem to have the same issue.
I can force an email to be sent from the 'Mail Server Settings' test email button, but don't get any during the normal use of SQL Response.
Can anyone confirm this issue?
Kev / comments
I seem to have the same issue.
I can force an email to be sent from the 'Mail Server Settings' test email button, but don't get any during the normal use of SQL Response.
Can anyone confirm this is...
I had the same, but seem to be having some success with Alerts if I go to Configuration > Base Monitor and update my base monitor connection config. In the file that was mentioned in the first error message "BaseLocation.config" I had <?xml version="1.0" encoding="utf-8"?> <baseMonitorLocations> <baseMonitorLocation networkName="localhost" portNum="7399"/> </baseMonitorLocations> but when I renamed the folder and let the installer recreate it I got <?xml version="1.0" encoding="utf-8"?>
<baseMonitorLocations>
<baseMonitorLocation networkName="" portNum="7399"/>
</baseMonitorLocations> Having now re-configured my base monitor to be localhost, SQM seems much happier [image] [image] Not sure on the "Monitoring errors" though, they still seem to be happening
/ comments
I had the same, but seem to be having some success with Alerts if I go to Configuration > Base Monitor and update my base monitor connection config. In the file that was mentioned in the first erro...