If you receive the below error while using the Availability Group Wizard you could try these steps to resolve it
First view the properties of the failed Replica
Make a note of the Endpoint port being used (In this case it was the default 5022)
Create a new Inbound Port Rule for the port on the Primary & Secondary servers
On the Secondary server (the one with the issue), right click on the database and select ‘Join to Availability Group’
Select ‘OK’
The database should now be joined
Hello!
I’m trying to test always on using two windows server 2008 r2 hyper-v virtual machines for both primary and secondary replicas.
I’m having trouble with joining error 35250. I’ve followed the steps shown in this post, but i doesn’t work.
I’ve turned off the firewall, but it stills shows error 35250.
Any idea ?
Thanks!
Hi Miguel,
if the firewall doesn’t appear to be the issue in your test scenario then I’d recommend slowly working through the various troubleshooting steps in the Microsoft article http://msdn.microsoft.com/en-us/library/ff878308.aspx and hopefully that will get it working for you.
You saved my day.
Hi,
I am also facing the same issue while setting up the ag. I tried the way u suggested and also microsoft suggestion https://msdn.microsoft.com/en-us/library/ff878308.aspx#JoinDbFails.
Can you specify some more approaches to resolve the same.
Thanks.