Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SQL 2008 Cluster monitoring

Hi,

We have a SQL 2008 Cluster that we are monitoring with ipMonitor. When we fail an instance from node 1 to node 2, the monitors carry on working happily. However, when we fail back to the original node 2, ipMonitor starts to generate these alerts. Any idea why?

cmsdbs (SQL Server (MSSQLSERVER))

status: Call was canceled by the message filter; oserror: 0x80010002

alert: 1 from a maximum of 1

critical failures: 1

Find more posts tagged with

Accepted answers

All comments

RhodanNZ

This seems to be intermittant. It generates an alert, sometimes a couple, for random services / drives that are being monitored on the cluster.

Perhaps our timings are too sensitive / too short for the monitors, or is it something with WMI?

Any recommendations / advice would be appreciated.

Peter.Cooper

Rhodan,

Forgive me... but can you tell me what monitor type is spitting out the error message. You did mention WMI, but I didn't want to assume.

Edit: Added "type" next to monitor.

RhodanNZ

Yes we are using WMI for these monitor's, as it's monitoring mount points which RPC does not seem to pick up, it just picks up the root drive. WMI is able to pick up the mount points on the root drive.

RhodanNZ

OK the failure can happen when failing over to either node. It's intermittant, and different monitor's fail each time, sometimes one, sometimes a couple.

I set the monitor to basically test twice before alerting, and that seems to have fixed it. I notice they do change to warn, and on the second test they change to up. Might be something to do with WMI by the looks of it.