Re: Database mirroring
- From: "Ayad Shammout" <ashammout1@xxxxxxxxxxx>
- Date: Wed, 12 Sep 2007 16:40:08 -0400
Check the following:
1.. Make sure that the mirror database is ready for mirroring.
2.. Make sure that the name and port of the mirror server instance are
correct.
3.. Make sure that the destination mirror server instance is not behind a
firewall.
4.. Make sure that the principal server instance is not behind a firewall.
5.. Verify that the endpoints are started on the partners by using the state
or state_desc column the of the sys.database_mirroring_endpoints catalog
view. If either endpoint is not started, execute an ALTER ENDPOINT statement
to start it.
6.. Make sure that the principal server instance is listening on the port
assigned to its database mirroring endpoint and that and the mirror server
instance is listening on its port. If a partner is not listening on its
assigned port, modify the database mirroring endpoint to listen on a
different port.
7.. Make sure that the SQL Server service account is a Domain account with
connect permission to each endpoint.
Ayad Shammout
"Manish Sukhija" <ManishSukhija@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:95381F96-A34A-4D99-9E31-12719452A11D@xxxxxxxxxxxxxxxx
Hi Guys,
I'm trying to configure mirroring among 3 servers,
principal,mirror,witness,
i was able to configure it successfully but when i start mirroring it
gives
this error the server network address "TCP://xx.yy.zz.com:5022" can not be
reached or doesn't exist. check the network address name and that the
ports
for the local and remote endpoints are operational(Microsoft sql server,
Error:1418)
I checked network address, all are correct, i don't why this error is
coming
.
- Prev by Date: Re: Failover Cluster Consumed - Now what?
- Next by Date: Re: Busy server, to cluster or not?...
- Previous by thread: Failover Cluster Consumed - Now what?
- Next by thread: Re: Busy server, to cluster or not?...
- Index(es):
Relevant Pages
|