Remove From My Forums

Failover Cluster - Failed to access remote regitry on 'SERVERNAME'

Question
0

Sign in to vote
Hello community,

I am trying to create failover cluster on Windows Server 2016, I create 3 virtual server for testing, in one of the server I set up the DNS and I tested and is fine. But when I try to "Validate Configuration" on the Failover Cluster Manager and enter the name of the server, it displays the following error messages:

"Failed to access remote registry on ''sql02.TESTDOMAIN.COM". Ensure that the remote registry service is running, and have remote administration enabled"

I enabled the Remote registry service and enabled the remote administration usgin gpedit.msc on Computer Configuration>Administrative Templates>Network>Network Connections>Windows Firewall enabling Domain Profile>Windows Firewall: Allow remote administration exception, then I checked the server manager to see if the remote management is enable on the 3 servers and it is.

This is my first time I am doing a this, so at this moment I am a little bit lost since I try everything that I read on the web.

Any advice o guidance would be really helpul.
- Edited by Asolano016 Wednesday, April 3, 2019 3:48 AM
Wednesday, April 3, 2019 3:32 AM

Answers

0

Sign in to vote
Hi,

Thanks for posting in our forum!

1. Double check your network configuration is no issue, It is recommended you specify the specific IP addresses [or subnet mask] for all Windows Server Cluster and SQL Server nodes/hosts [including Availability Group Listeners] so the firewall rules will work properly.

SPECIAL NOTE: You need to review and modify, if needed, the dynamic port ranges on each Windows Server Cluster nodes/hosts to a company/policy acceptable range for certain dynamic TCP/UDP traffic.

For more information, please see here:

https://social.technet.microsoft.com/Forums/windows/en-US/db49fe6a-c231-4088-9025-0e8f3f4fb7be/windows-server-failover-cluster?forum=winserverClustering

http://dsfnet.blogspot.com/2013/04/windows-server-clustering-sql-server.html

2. Please Enable Remote Registry and Windows Management Instrumentation Services.

https://helpcenter.netwrix.com/Configure_IT_Infrastructure/Windows_Server/Enable_Remote_Registry.html

3. Try to upgrade your server and try again.

4. Please check if there is any error Event ID in Event viewer.

5. Try running “winrm quickconfig” from command prompt and see if it gives you any info that helps.

6. Try to use Administrator account and try again.

7. Disabling IP v 6 and enabling Client for Microsoft network and File and Printer sharing.

8. Uninstall any AV software and try again.

For more information, please visit:

https://social.technet.microsoft.com/Forums/Lync/en-US/e0e42647-ffb1-4393-9c1e-9d0e78cbd374/validation-failed-on-remote-server-ensure-that-the-remote-registry-service-is-running-and-have?forum=winserverClustering

Hope this information can help you, if you have any question, please feel free to let me know.

Best Regards,

Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
- Marked as answer by Asolano016 Tuesday, April 9, 2019 4:21 AM
Wednesday, April 3, 2019 7:25 AM

All replies

0

Sign in to vote
Hi,

Thanks for posting in our forum!

1. Double check your network configuration is no issue, It is recommended you specify the specific IP addresses [or subnet mask] for all Windows Server Cluster and SQL Server nodes/hosts [including Availability Group Listeners] so the firewall rules will work properly.

SPECIAL NOTE: You need to review and modify, if needed, the dynamic port ranges on each Windows Server Cluster nodes/hosts to a company/policy acceptable range for certain dynamic TCP/UDP traffic.

For more information, please see here:

https://social.technet.microsoft.com/Forums/windows/en-US/db49fe6a-c231-4088-9025-0e8f3f4fb7be/windows-server-failover-cluster?forum=winserverClustering

http://dsfnet.blogspot.com/2013/04/windows-server-clustering-sql-server.html

2. Please Enable Remote Registry and Windows Management Instrumentation Services.

https://helpcenter.netwrix.com/Configure_IT_Infrastructure/Windows_Server/Enable_Remote_Registry.html

3. Try to upgrade your server and try again.

4. Please check if there is any error Event ID in Event viewer.

5. Try running “winrm quickconfig” from command prompt and see if it gives you any info that helps.

6. Try to use Administrator account and try again.

7. Disabling IP v 6 and enabling Client for Microsoft network and File and Printer sharing.

8. Uninstall any AV software and try again.

For more information, please visit:

https://social.technet.microsoft.com/Forums/Lync/en-US/e0e42647-ffb1-4393-9c1e-9d0e78cbd374/validation-failed-on-remote-server-ensure-that-the-remote-registry-service-is-running-and-have?forum=winserverClustering

Hope this information can help you, if you have any question, please feel free to let me know.

Best Regards,

Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
- Marked as answer by Asolano016 Tuesday, April 9, 2019 4:21 AM
Wednesday, April 3, 2019 7:25 AM
0

Sign in to vote

Hello Daniel,

Thank you for your guidance, I'm going to check your comments.

Wednesday, April 3, 2019 4:48 PM
0

Sign in to vote

OK, let me know if you have any question.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Thursday, April 4, 2019 1:48 AM
0

Sign in to vote

Any update?

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Monday, April 8, 2019 1:56 AM
0

Sign in to vote

Hi Daniel,

I tried the instrucctions that you provided me, but the same error keep showing up. I disable the firewalls in order to test and I start receiving a access error message. Then I execute the winrm quickconfig command as an admin and then I get back to the same error message.

I am using 3 vmware virtual machines, the DNS with the default gateway for each server seems to be working when I make a ping to the DNS name to the servers but I don't if I am missing something else on the DNS configuration, in the VM configuration or in the security of the server.

Monday, April 8, 2019 5:45 PM
0

Sign in to vote

I'm really sorry to hear that!

Try to disable file and print sharing in the network adapter properties and try again.

It looks like you have a problem with your network configuration. Have you ever asked a network expert?

https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverNIS

You can also ask VMWare experts here：

https://communities.vmware.com/welcome

Hope this information can help you.

Best Regards,

Daniel

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Tuesday, April 9, 2019 1:55 AM

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support options

More support

Not an IT pro?

Answered by:

Failover Cluster - Failed to access remote regitry on 'SERVERNAME'

Question

Answers

All replies