Comments
Sort by recent activity
Could the size of your error logs be an issue?
Are you recycling them?
Do they take a long time to open in SSMS? / comments
Could the size of your error logs be an issue?
Are you recycling them?
Do they take a long time to open in SSMS?
Update for anyone stumbling across this thread - it has been logged as a bug.
Kev / comments
Update for anyone stumbling across this thread - it has been logged as a bug.
Kev
An update...
I changed the gateway of the alert repository pc to avoid the proxy(MS ISA Server) to see if that had any effect - it didn't.
Put the machine back on the proxy, and since then haven't had a repeat of the issue.
So as far as it seems, it was just a temporary issue that seems to have 'fixed' itself.
Kev / comments
An update...
I changed the gateway of the alert repository pc to avoid the proxy(MS ISA Server) to see if that had any effect - it didn't.
Put the machine back on the proxy, and since then haven't ...
Not sure if this is related .....
now getting 'Computer unreachable' alerts, with the log entry of
ServerUpMonitor: COM Error 0x800706A from xxx.xxx.xxx.xxx
Any ideas?
Kev / comments
Not sure if this is related .....
now getting 'Computer unreachable' alerts, with the log entry of
ServerUpMonitor: COM Error 0x800706A from xxx.xxx.xxx.xxx
Any ideas?
Kev
Daniel,
will do. Should I use support@red-gate.com?
How do you want the data? Job history I could export to Excel.
Alerts - how do you want these?
Kev / comments
Daniel,
will do. Should I use support@red-gate.com?
How do you want the data? Job history I could export to Excel.
Alerts - how do you want these?
Kev
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 ...