- Mais recentes
- Mais votos
- Mais comentários
I checked the event log of the server in which I am configuring the Windows Failover cluster. It shows the following log immediately after the addition of the secondary node fails.
DCOM was unable to communicate with the computer xxx.xxx.xxx.xxx; requested by PID 1530 (C:\Windows\system32\mmc.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}. using any of the configured protocol. The CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} belongs to the Windows Management Instrumentation service.
I hope this should help understand the cause and the resolution.
The issue is resolved now. I enabled all traffic access to the subnet group and that resolved the issue.
The issue has been fixed by me. I have added the solution in the post.
Hi,
Thanks for updating the thread and sharing the resolution.
Since the issue is already resolved by you, we can mark this thread as closed.
Conteúdo relevante
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 meses
- AWS OFICIALAtualizada há 2 anos