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

Monitoring Sqlserver.exe in a clustered environment.

I have two servers SRVa and SRVb with a virtual cluster name of SRVcluster. If I check for the SQLServer service on SRVa and it is the active cluster it is successful. If I check SRVb it fails because it is not the active cluster. If I try using this same monitor for SRVcluster I get the following error.

Testing on node SRVcluster: failed with 'Undefined' status

Object reference not set to an instance of an object.

What do recommend I do to fix this. I cannot have this many failures showing up on a daily basis. I have six SQL server clusters(12 servers).

Find more posts tagged with

Accepted answers

All comments

mcbridea

Would it work for you to unmanage the secondary and only manage the primary?

rbrault

The only thing is, currently my b node is active and I am not allowed to just failover during the day(Rules... who needs 'em.) I will need to know if the service was to die on the B node now.

mcbridea

Hmmm. Maybe someone from our user community has solved this?

TGhosh

I have several MS Clusters running SQL Server 2005 in my environment

I add all three nodes. The primary and secondary nodes are added with their actual IP's and I select all resources for each node (CPU, Memory, Disks, Network interfaces)

I add the Cluster node via the SQL Cluster IP (not the MS cluster IP). under this node, I add all viewable resources (be sure to add the MS Virtual Cluster NIC)

If you have APM 3.0, apply the SQL 2005 APM Template to the Cluster node you previously added.

During a cluster failover, you should get several alerts from the Virtual cluster adapter as well as the disc resources which should flip from the one node to the other. It seems to work pretty well for us. We've even been able to spot when the cluster failover doesn't take place as expected since the MS Virtual cluster adapter on the Cluster Node does not come back up.

Sorry if the explanation was confusing. Let me know if you have questions.

What hardware are you monitoring?