January 17, 2012 at 8:32 am
I have sql server 2008 on windows 2008
Mirror configured with Witness(Certificate authentication)
today I found that Mirror disconnected state.I got the below error on SQL Error log on primary server
Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://wedcb469:5023'.
2012-01-17 02:04:01.090 spid20s Error: 1474, Severity: 16, State: 1.
I am able to connect Primary ,Witness and Mirror servers from all 3 servers
but still mirror is in disconnected state.
I found one more error on errorlog.
An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '')
can somebody help me on this
January 17, 2012 at 8:43 am
Can you resume the mirroring session? A network outage of more than (x) minutes will put the session into a suspended state. I dont know what the value of x is, but I have experienced this issue many times.
ALTER DATABASE <database_name> SET PARTNER RESUME
January 17, 2012 at 2:37 pm
this is more than likely a DNS issue.
trouble shoot by using ping or nslookup on the witness and make sure they both resolve.
January 23, 2012 at 12:46 am
Recently days, I have encountered the same issue of my production SQL Server 2008 database mirror and I fixed it as following:
on the mirror server
use master
GO
alter endpoint endpoint_name state = stopped;
GO
alter endpoint endpoint_name state = started;
GO
may you success!
June 19, 2012 at 9:05 am
cherish.j.wang (1/23/2012)
Recently days, I have encountered the same issue of my production SQL Server 2008 database mirror and I fixed it as following:on the mirror server
use master
GO
alter endpoint endpoint_name state = stopped;
GO
alter endpoint endpoint_name state = started;
GO
may you success!
Nice one, it works fine!! Thanks a lot!
June 20, 2012 at 9:02 am
You are less likely to have a name resolution problem if you use the fully qualified domain name of the servers. Name resolution is probably the root cause of the issue. Then you encountered a "poisoned queue" issue. Mirroring is built on top of the service broker engine, and too many consecutive errors will cause the queue behind the endpoint to shut down (the endpoint is still running, but the queue behind it is not).
cherish.j.wang showed you how to get the queue to start up again, but the root cause may still need to be addressed.
June 21, 2012 at 8:36 am
Robert Davis (6/20/2012)
You are less likely to have a name resolution problem if you use the fully qualified domain name of the servers. Name resolution is probably the root cause of the issue. Then you encountered a "poisoned queue" issue. Mirroring is built on top of the service broker engine, and too many consecutive errors will cause the queue behind the endpoint to shut down (the endpoint is still running, but the queue behind it is not).cherish.j.wang showed you how to get the queue to start up again, but the root cause may still need to be addressed.
Robert is correctly. I don't the root cause yet. I have came across this issue of mirroring many time and fixed it via restart endpoint already.;-)
June 21, 2012 at 8:44 am
Robert Davis (6/20/2012)
You are less likely to have a name resolution problem if you use the fully qualified domain name of the servers. Name resolution is probably the root cause of the issue. Then you encountered a "poisoned queue" issue. Mirroring is built on top of the service broker engine, and too many consecutive errors will cause the queue behind the endpoint to shut down (the endpoint is still running, but the queue behind it is not).cherish.j.wang showed you how to get the queue to start up again, but the root cause may still need to be addressed.
Robert is correctly. I don't the root cause yet. I have came across this issue of mirroring many time and fixed it via restart endpoint already.;-)
July 9, 2012 at 5:24 am
Restarting your DNS will resolve the issue.
“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris
July 17, 2012 at 10:43 am
General question here. Anyone got an idea on how to get alerted/notified/emailed on this. Our server actually went down and we didn't know the witness couldn't see the mirror, so no automatic failover.
Thoughts?
Fraggle
July 17, 2012 at 11:08 am
Look up "database mirroring [SQL Server], monitoring" in Books Online for the basic stuff. Buy my book and/or read my blog for the advanced stuff.
September 20, 2012 at 12:56 pm
A note on resetting the endpoints. It will take your database offline for the duration of the restart. This is "expected" behavior per Microsoft support that hasn't been documented. If the endpoint is left off on the principal, then the server will failover.
Fraggle
April 20, 2014 at 1:10 pm
Does Mirroring Break if we stop and start the Endpoints!!!!!!?????
April 20, 2014 at 1:31 pm
Pavan.g (4/20/2014)
Does Mirroring Break if we stop and start the Endpoints!!!!!!?????
It doesn't break. It will stop running when the endpoint is stopped and start running again when it is restarted.
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply