Cluster Not showing up in FailOver Cluster Manager on the Node

[razhamma]

Hi team,

I tried deploying this quickstart with SQL 2017/2019 with launching into an existing VPC(given that VPC networking configs were perfect as expected and were automatically set up by Active Directory Domain Services on AWS quickstart using Scenario 3 with into a new VPC option)

• Stack was created successfully with SQL 2017.
• Stack failed with SQL 2019.

However, upon performing Post-Launch Steps:

With SQL 2017:

• Running Get-ClusterGroup for the second time started showing status for "Cluster Group" as PartialOnline.
• Manually, trying to connect to Cluster by using name WSFCNode1 through "Failover Clustering Manager" fails with error "AccessDenied".
• Running "Validate a Configuration" wizard and loading WSFCNode1 and WSFCNode2 on WSFCNode1 itself also fails with error as "You do not have Administrator privileges for WSFCnode2.

With SQL 2019:

• Stack creation failed on waiting for SSMWaitCondition resource with error message as "Received FAILURE signal with UniqueId instance_id.
• Stack remained in CREATE_IN_PROGRESS for more than 2 hours.
• Upon logging into the respective instance, I couldn't find any logs at following locations as well

%ProgramFiles%\Amazon\EC2ConfigService 
C:\cfn\log

Ask:

• Please help in troubleshooting as I don't have enough insights into what's missing.
• Also, this quickstart is a hard dependency for SharePoint Server on AWS quickstart so please identify and release fix asap.

Thanks,

[john143143]

Hi @razhamma , I’m facing the same issue. May I know how did you fix that?

[razhamma]

Hi @johnkennady04, have you tried this -> SQL Server with Always On Replication on the AWS Cloud Quick Start Reference Deployment.

Looks like a new updated guide dropped just a few days ago.

[john143143]

Yes I tried.