March 26, 2012 at 3:54 pm
I am trying to implement mirroring on the local machine b/w two instances on the same machine.
But I get the following error.
One or more of the server network addresses lacks a fully qualified domain name (FQDN). Specify the FQDN for each server, and click Start Mirroring again.
The syntax for a fully-qualified TCP address is:
TCP://<computer_name>.<domain_segment>[.<domain_segment>]:<port>
I am on the same local machine. So I cannot give the domain name. There is machineName:Portnumber on both the Principle and Mirrored instances.
It is not allowing me to do mirroring.
What could I do to resolve this issue?
March 26, 2012 at 4:02 pm
Computer name is the name of your computer.
If mirroring between instances on the same server, you have to use different ports for each instance.
March 26, 2012 at 4:07 pm
They do have different ports assigned.
Principle: TCP://CompName:5022
Mirrored: TCP://CompName:5023
Even then I get the error.
I am using 2005 and I am working on Win7. If that will make any difference.
Regards,
Nawaz.
March 26, 2012 at 4:10 pm
na1774 (3/26/2012)
They do have different ports assigned.Principle: TCP://CompName:5022
Mirrored: TCP://CompName:5023
Even then I get the error.
I am using 2005 and I am working on Win7. If that will make any difference.
Regards,
Nawaz.
If you are connecting a named instance, the instance name needs to be in there as well.
March 26, 2012 at 4:26 pm
Priciple: TCP://Nawaz-PC:5022
Mirror: TCP://cOMPUTERnAME.INSName:5023
Even Then I get the error.
March 26, 2012 at 4:28 pm
na1774 (3/26/2012)
Priciple: TCP://Nawaz-PC:5022Mirror: TCP://cOMPUTERnAME.INSName:5023
Even Then I get the error.
I am not sure of the format when mirroring to a named instance. When I established mirroring in a production environment it was between default instances on separate servers. I will have to do some research to figure at what may be wrong with your code.
March 26, 2012 at 8:52 pm
Any way Thanks u for the help.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply