Failover SQL instance has no remote registry service

Charlie 96 Reputation points
2021-10-14T12:36:20.667+00:00

I'm having some issues with SQL after upgrading the underlying VM's in the failover cluster. Specifically, the sqlserver name has no remote registry available. It's a 2 node, server 2019 cluster with sql2019 on it. I am able to access remote registry for both of the cluster nodes, but not the sql server name itself. This presents a problem for things like SCCM which try to connect to the remote registry on that name. I have done a ton of searching, but obviously not asking the right thing. SQL itself is working fine and all the resources come up and work (at least the ones listed). I temporarily turned off the firewall as a hail mary, that didn't help. I have a lot of experience in the CM/Server side of things, but definitely am not a SQL DB. Any advice on where to look? Thank you!

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,709 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
958 questions
Microsoft Configuration Manager
Accepted answer
  1. Charlie 96 Reputation points
    2021-10-21T17:45:49.743+00:00

    Found a resolution finally. Randomly figured out it was only 1 of the 2 failover nodes having the issue (same issue presented for a file share). Ended up setting up a new VM in its place and it worked out fine. Not sure why SMB was having an issue on only 1 server, but its fixed now. Wish I knew the root cause/fix though.

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. YufeiShao-msft 7,056 Reputation points
    2021-10-15T03:08:06.077+00:00

    Hi @Charlie ,

    you can check your error log for exceptions that occur, double check your network configuration is no issue, it is recommended you specify the specific IP adresses (or subnet mask) for all Windows Server Cluster and SQL Server nodes/hosts (including Availability Group Listeners) so the firewall rules will work properly.
    you can refer to this biog:http://dsfnet.blogspot.com/2013/04/windows-server-clustering-sql-server.html

    please Enable Remote Registry and Windows Management Instrumentation Services:https://helpcenter.netwrix.com/NA/Configure_IT_Infrastructure/Windows_Server/Enable_Remote_Registry.html

    Your problem may be due to the occurrence of “The resource type is not registered in the WSFC cluster”
    so check the PowerShell to get resource type and found below: 

    Get-ClusterResourceType | where name -like "SQL Server Availability Group"

    and then register the resource type manully using below PowerShell: 

    Add-ClusterResourceType -Name "SQL Server Availability Group" -DisplayName "SQL Server Availability Group" -Dll "C:\Windows\System32\hadrres.dll"

    https://blog.sqlauthority.com/2019/01/03/sql-server-fix-msg-41105-failed-to-create-the-windows-server-failover-clustering-wsfc-resource-with-name-and-type-sql-server-availability-group/

    you can try to re-create the resource-specific registry keys:https://learn.microsoft.com/en-us/troubleshoot/sql/failover-clusters/manually-re-create-resource-specific-registry-keys

    -------
    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    0 comments
  2. Charlie 96 Reputation points
    2021-10-20T13:22:43.47+00:00

    Sorry for the late reply (for some reason I didn't get notified there was another reply). When I run that first PS command, I get back the group as expected. I did end up opening the firewall fully just for testing reasons, but that did not help.

    I eventually did a wireshark session and when I try to connect via the FQDN, I get back "Error: STATUS_OBJECT_NAME_NOT_FOUND" response from SMB2. Like I said, connecting via the IP for the sql cluster works fine though.

    0 comments