Activity overview
Latest activity by Vulcan
Hi,
We have had a very similar issue with a 2016 availability group and are not able to use our SQL monitor licenses at all since upgrading SQL.
Here’s a quick run-down of we've looked at and tested:
- When adding the VUL-SQL-01 server, it correctly queries the WMI and finds the cluster name. But when it tries to query the WMI repository using the cluster name it fails.
- we’ve tested a WMI query remotely, which succeeded, so WMI is working fine and open for remote queries.
- As we know SQL remote connections are working ok.
- we’ve tested our agent account and it can connect and query WMI, and is a local admin on the DB servers.
- we’ve gone through all the connection tests that are listed on the Red-Gate support site. And they all work fine talking to the local server, but not to the cluster name.
- we’ve checked the cluster permissions, and the local admin group has full control over the cluster, and the SQLMonitor.Agent account is a local admin. So it’s not a permissions issue.
But none of that has fixed the connection issue.
My suspicion is the changes to clustering in Windows 2016 has broken how SQL Monitor connects. But it’s just a suspicion.
Thanks,
Tane / comments
Hi,
We have had a very similar issue with a 2016 availability group and are not able to use our SQL monitor licenses at all since upgrading SQL.
Here’s a quick run-down of we've looked at and teste...