July 27, 2015 at 9:21 pm
HI,
I am working on configuring SQL 2014 alwayson and encountering this error "SQL AlwaysOn: Failed to join the database to the Availability Group (Error 35250)" and
followed all steps according to this msdn link. and matched with last error- DNS error. SO now i would like to know how to resolve this issue as network team is saying that there is no issue at DNS end.
http://blogs.msdn.com/b/alwaysonpro/archive/2013/12/09/trouble-shoot-error.aspx
When i run the query:select r.replica_server_name, r.endpoint_url,
rs.connected_state_desc, rs.last_connect_error_description,
rs.last_connect_error_number, rs.last_connect_error_timestamp
from sys.dm_hadr_availability_replica_states rs join sys.availability_replicas r
on rs.replica_id=r.replica_id
where rs.is_local=1
the last_connect_error_description is returned as "Connection attempt failed with error: '10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)'. "
and last_connect_error_number=10060
connected_state_desc='disconnected'
Please help.
July 28, 2015 at 4:21 pm
I would use tracert, ping, and pathping to look for performance issues. This sounds like a network problem, it's not going to be super easy to diagnose.
I would also increase your session timeout setting in the AG from the default of 60 to something higher like 120 or 240 and see what happens.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy