Activity overview
Latest activity by ScottHerbert
I've re-emailed, from Scott dot Herbert at arc dot gov dot au / comments
I've re-emailed, from Scott dot Herbert at arc dot gov dot au
Hi Chris,
I've emailed you the logs.
Thanks,
Scott / comments
Hi Chris,
I've emailed you the logs.
Thanks,
Scott
Never mind,
looks like I was not reading the "Type machine-name\* to add all the SQL Server instances on a machine" instruction...
:mrgreen: / comments
Never mind,
looks like I was not reading the "Type machine-name\* to add all the SQL Server instances on a machine" instruction...
:mrgreen:
Interestingly, when i removed and re-added the server in SQL Monitor, then forced a deadlock, the alert started appearing.
So it looks to me to be a bug with SQL monitor. / comments
Interestingly, when i removed and re-added the server in SQL Monitor, then forced a deadlock, the alert started appearing.
So it looks to me to be a bug with SQL monitor.
Adding a cluster: not recognising instances
I've been having some trouble with alerts showing up on our prod cluster, so I tried removing it completely from SQL monitor, and re-adding it.
When adding a new server, I pick the server name, and...
I can't find any good information about this error online but I'd be surprised if it was related to SQL Monitor not creating deadlock alerts.
Unfortunately I think it's barking up the wrong tree, as I just forced a deadlock on my LAB box, got the same weird message in the LAB SQL Log, but happily rec'd an alert in SQL Monitor.
Are deadlock alerts are definitely enabled for this specific server in the Alert Settings page?
Deadlock alerts are definitely enabled: we haven't really played at all with alert levels or en/disabling.
Also could we have a few details of the server in question so that I can run some tests? For example, sql server version, clustered or standalone etc.
SQL Server 2008 R2, Clustered active/active with 3 instances.
The SQL Monitor service account is admin on the machine and has sysadmin in SQL.
I've also noticed the lack of all other alerts for one of the instances on the cluster. / comments
I can't find any good information about this error online but I'd be surprised if it was related to SQL Monitor not creating deadlock alerts.
Unfortunately I think it's barking up the wrong tr...
Are there any warnings/errors in the 'Show Log' page linked from the Monitored Servers page for each server?
I forced a deadlock, and there are no errors shown in the Show log page at all for that server. However I do note in the SQL Log itself that amongst the many lines of info for the deadlock that occurred, there's an entry that says "Log viewer could not read information for this log entry. Cause: Data is Null. This method or property cannot be called on Null Values.. Content:"
As SQL Monitor gets its deadlock information from the SQL error logs, and deadlocks are definitely appearing there, it suggests that the software might be having problems accessing the logs. Maybe due to a permission issue as we use remote file access to read the SQL Logs. If errors do exist we have a troubleshooting page that includes details on testing remote file access:
I think a permissions issue is unlikely as the the SQL Monitor service account is a member of the Administrators group on the monitored server. Also, I've not noticed any other alerts not appearing; for example high processor usage alerts are popping up as expected.
Another possibility - is the 1204 trace flag enabled for the servers in question?
Yes, it's enabled. / comments
Are there any warnings/errors in the 'Show Log' page linked from the Monitored Servers page for each server?
I forced a deadlock, and there are no errors shown in the Show log page at all for ...
Deadlocks not being captured
I'm running SQL Monitor against several environments.
In our test/dev envs, I'm getting alerts when deadlocks occur.
However in prod, I can see deadlocks in the SQL Logs, but no alert in SQL Mon.
Thanks Priya, that makes sense as to why it's been implemented like that. / comments
Thanks Priya, that makes sense as to why it's been implemented like that.
Retry Connection after Monitoring Stopped
Hi,
Is there a way to configure an amount of time after which SQL Monitor will attempt to reconnect to a server which has become unreachable?
We are monitoring a SQL2008R2 Failover Cluster which si...