February 7, 2008 at 1:26 pm
I am attempting to mirror a SQL database. I ran a full backup of the primary database (RESTORE WITH NORECOVERY) to the mirror server.
When I created the mirror (on the primary) server I get the following message:
The server network address "TCP://servername:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.
The port is not blocked. I can ping both servers from one another. I am using the same SA account on both servers.
Any insight?
Thanks,
Kerry
February 7, 2008 at 11:31 pm
Pls check the below links,
http://msdn2.microsoft.com/en-us/library/ms189127.aspx
http://msdn2.microsoft.com/en-us/library/aa337361.aspx
There are 2 possibilities namely,
1. The port you specified might have been already used or blocked.
2. While restoring you need to restore Full backup using With Norecovery and then restore one transactional log backup using With Norecovery clause and then only start mirroring.
Try to alter the endpoint and specify different port number and then start mirroring it might work...You can refer this link for configuring mirroring, screenshots for each and every step is available..
http://sql-articles.com/index.php?page=articles/dbmrr.htm
[font="Verdana"]- Deepak[/font]
February 8, 2008 at 2:55 am
Hi
In my experience the TCP endpoint address is not always tcp://servername:5022
If your host has a DNS suffix i.e the fully qualified domain name is "servername.ssc.com", the endpoint address will be tcp://servername.ssc.com:5022
If you ping servername, the reponse will contain the FQDN
HTH
Rich
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply