The RPC server is unavailable
Hermes
Posts: 4 New member
Hello,
My boss asked me to try and choose best monitoring tool for our SQL Servers. I am trying Red-gate SQL Monitor 7.1.1.8196 now.
I am facing problem with configuration monitored servers. Monitoring status is Unreachable / Cannot connect
with exception message The RPC server is unavailable. (Exception from HRESULT: 0x800706BA).
Group WMI - GetInstances: root\cimv2 select ContextSwitchesPersec,ProcessorQueueLength,SystemUpTime from Win32_PerfRawData_PerfOS_System.
Monitoring tool is running on same server as monitored named instances and administrator account is used.
Can you help me to solve this problem please ?
OS : Windows Server 2016, MS SQL 2016
My boss asked me to try and choose best monitoring tool for our SQL Servers. I am trying Red-gate SQL Monitor 7.1.1.8196 now.
I am facing problem with configuration monitored servers. Monitoring status is Unreachable / Cannot connect
with exception message The RPC server is unavailable. (Exception from HRESULT: 0x800706BA).
Group WMI - GetInstances: root\cimv2 select ContextSwitchesPersec,ProcessorQueueLength,SystemUpTime from Win32_PerfRawData_PerfOS_System.
Monitoring tool is running on same server as monitored named instances and administrator account is used.
Can you help me to solve this problem please ?
OS : Windows Server 2016, MS SQL 2016
Tagged:
Comments
i have checked all this steps before.
I checked WMI by WMI Tester and WMI Tester tool is working without problems.
Same exception message.
I am just trying to get this setup on my local machine first for a trial and then to go from there.
Also its intermittent - you restart the service, no Monitoring error
20 minutes later - Monitoring error. I have never come across an intermittent firewall issue in the last 20 years of IT but I am willing to accept that you cannot fix it.
I have a support ticket open and the logs were sent, they are equally baffled. The only logical explanation is bad code; because we have never had this issue before upgrading to v10.1.5 which is the latest version.
I finally tried deleting and readding the SQL instance is the monitoring tool and then was provided a different WMI error.
My issues were apparently related to Windows Performance counters simply not working or were missing.
Hopefully, that can fix your problem as it resolved my issue.
Should probably go in the main trouble shooting guide after you run through the standard connection tests.