Skip to main content

MSSQL AAG Replica secondary showing disconnected error

 Error:


You will see the secondary replica is disconnected error as:


Solution:


In this case go to SQL server and check the ERROR log and see the exact error:

Error Log location:

C:\Program Files\Microsoft SQL Server\<MSSQL15.MSSQLSERVER>\MSSQL\Log

I am able to see the error as :


There is no user and permisions.

On Node2 from SQL query run:

GO
CREATE LOGIN [RAN\SQL-AG-VM-Node1$] FROM WINDOWS
GO
GRANT CONNECT ON ENDPOINT::hadr_endpoint TO [RAN\SQL-AG-VM-Node1$];
GO

On Node2 run SQL query

GO
CREATE LOGIN [RAN\SQL-AG-VM-Node2$] FROM WINDOWS
GO
GRANT CONNECT ON ENDPOINT::hadr_endpoint TO [RAN\SQL-AG-VM-Node2$];
GO


Now try a failover and you will see both in CONNECTED





Comments

Popular posts from this blog

Deploy OVF fails Issues detected with selected template. Details: VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 Error: While deploy using OVF file ,getting error as : Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19]. Solution: Open .OVF file and edit       <Info>Virtual hardware requirements for a virtual machine</Info>       <System>         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>         <vssd:InstanceID>0</vssd:InstanceID>         <vssd:VirtualSystemIdentifier>zabbix_appliance-6.2.7</vssd:VirtualSystemIdentifier>         <vssd:VirtualSystemType> virtualbox-2.2 </vssd:VirtualSystemType>       </System> to  vmx-19       <Info>Virtual hardware requireme...

Change ESXi acceptane level of VIBs to community Supported

-When you install VIB bundles you may see issue like:               'Could not find a trusted signer: self signed certificate  For resolving this issue, we have to convert the ESXi to community supported acceptance level. -To do that: if  ESXI is a VM :      Edit settings ->boot option ->disable secure boot. if Physical ESXi:      Edit  UEFI Now ssh to ESXi: - Move the ESX machine to community-support esxcli software acceptance set --level=CommunitySupported - Install the bundle with no-sign-check esxcli software vib install -d  VMware_bootbank_vmware-fdm_7.0.1-16478307.vib --no-sig-check -  Set back PartnerSupported esxcli software acceptance set --level=PartnerSupported