Trouble setting up monitoring on a cluster
scubamandan
Posts: 5
Hi. I have an active/passive cluster that I can't seem to set up. I get the following error: "Unreachable Cannot connect"
And in the logs:
GROUP EVENT OUTCOME EXCEPTION EXCEPTION MESSAGE
Registry OpenRegistryHive: LocalMachine Cannot connect Win32Exception The network path was not found
I've tried following the steps here:
https://documentation.red-gate.com/display/SM5/Testing+data+collection+methods
From the base machine (doubles as web host) I can ping the nodes as well as the Cluster name, I can also connect to the registry remotely as well as perfmon using the required user.. I'm assuming the problem is network one, but if I'm passing the tests, how I could I be failing to connect?
What else can I check? Anyone have any ideas? It'd much appreciated.
And in the logs:
GROUP EVENT OUTCOME EXCEPTION EXCEPTION MESSAGE
Registry OpenRegistryHive: LocalMachine Cannot connect Win32Exception The network path was not found
I've tried following the steps here:
https://documentation.red-gate.com/display/SM5/Testing+data+collection+methods
From the base machine (doubles as web host) I can ping the nodes as well as the Cluster name, I can also connect to the registry remotely as well as perfmon using the required user.. I'm assuming the problem is network one, but if I'm passing the tests, how I could I be failing to connect?
What else can I check? Anyone have any ideas? It'd much appreciated.
Comments
Usually when there is an issue like this with a cluster this ends up being the answer - see the quote box at the bottom.
Please let us know if that helps resolve the issue!
Kind regards,
Alex
Have you visited our Help Center?
Should I be testing from the SQL monitor service to the nodes, or to the Cluster Name? i.e. testing remote registry and WMI.
You should be testing from the SQL Monitor machine as the user SQL Monitor uses to whichever element is having the problem - so if it's a node, standalone server or the cluster name itself - test to that entity.
Kind regards,
Alex
Have you visited our Help Center?
Sorry, my last message was a bit unclear - I had said "...to whichever element is having the problem - so if it's a node, standalone server or the cluster name itself - test to that entity." meaning it should be to the cluster name if that was where the error was displaying - but you indicated you have tried to both the node and cluster names and it is working properly. I have just received your support ticket and will continue troubleshooting there and then post whatever resolution we find here.
Kind regards,
Alex
Have you visited our Help Center?