How can we help you today? How can we help you today?

Single server previously in a cluster cannot be monitored

Hi all,
We have a SQL 2008 machine to be replaced but still running production. Before this was a cluster but now we use the primary node as a single instance.
However: Redgate will not register it because the cluster service gives WMI errors.

So this not only costs 2 licenses but there's no monitoring possible.

There really should be an option to monitor a single instance that is part of a (previous) cluster.

Any thoughts?

Regards,
Hans van Dam
Hans_van_Dam
0

Comments

2 comments

Sort by
  • Russell D
    This is often a result of the removal of the clustering roles not working properly. It's a known Windows issue.

    If removing and deleting the data then re-adding isn't working, rebuilding the cluster namespace can help. In an elevated command prompt, can you please navigate to C:\Windows\System32\wbem, and run 
    mofcomp.exe ClusWMIUninstall.mof

    then restart the Windows Management Instrumentation service. Completely remove the server from Monitor and then try re-adding it.

    Russell D
    0
  • Hans_van_Dam
    Thanks for this fix, but it appears I made a mistake so I'll save it for maybe later.
    This is not a failover cluster like the other ones we have, but an older SQL Cluster, so 2 nodes of which 1 active as SQL Server. All services are up but it seems Redgate does not have all necessary rights, working on that now.
    Hans_van_Dam
    0

Add comment

Please sign in to leave a comment.