ali_khankan


Hello Guys,

I had been trying to solve this error with no success :

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 had installed three instances on my local machine to test Data base mirroring :

Principal : running SQL Developer Instance

Mirror : running SQL Developer Instance .

Witness : Running SQL Express.

Database mirroring already enabled using startup flag : -T1400

i even tried to configure it with out a witness but still have the same error .

I used the follwoing server name in the mirroring wizard(not localhost) :

Principal : TCP://Ali-laptop:5022

Mirrored : TCP://Ali-laptop:5023

Witness : TCP://Ali-laptop:5044

whats the problem guys !




Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

Satya SKJ


Can you ping the server using FQDN (fully qualified domain name)





Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

ali_khankan

yes sure ,i mentioned that ALL instances are running on a single machine.




Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

ali_khankan

Guys, any bright ideas !



Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

TomPullen

Did you restore the database WITH NORECOVERY The error about FDQNs is spurious sometimes.



Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

Brian W. King

Hmmm. The wizard seems to suck a bit. It only handles one scenario, with all machine participating in a domain. Change the machine names to IP addresses of the machines. So it will read "TCP://192.168.0.8:5022 or what ever your IP and ports are set to. I also had to use certificates to get it to work in my instances (high safety and availability). Two must reads from MS on this are "Achieve High Availability for SQL server" and "Using Certificates for Database Mirroring" These are the ONLY two MS articles that will address certificates. They are not complete and you still need more info. "Database Mirroring in SQL Server 2005" is also a required document to get it working, but they do not address a setup correctly if you want High safety and availability. The first two docs I mentioned take precidence and then the information they lack, you have to backfill with the third.

I ended up with a thirty page how to guide for my scenario when I finally got it working. Hte trick was really the swapping f the machine names with the IPs. That did the trick for me.

Sorry about the lack of links to the MS docs. The doc names are vebatum so you can esily search for them. Sorry there is no easy answer either. MS needs some serious work on the wizard at the moment, but it is a decent first stab at it. The mirroring works great once it is established. I would recommend it in opposition to other methods. Setup is painfull however.






Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

Brian W. King

BTW - I could NOT use the wizard as it does not allow for IP addresses. You must use SQL commands. The documents spell them out.




Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

ali_khankan

thanks for all replies ,but this is really frustrating ,i follow ALL instruction to apply one of the NEWEST technologies MS boasts ,step by step ,i restored the mirror in no recovery mode ,stupid wizard always taking me back to the same place ,my server naming has a problem! ,i changed my server name to be :localhost so the wizard can capture :

TCP://localhost:5023

still getting the same misleading error ,i was NOT able to change my machine name to an IP address as windows XP doesnt allow special characters in a machine name ,i am starting to think by default the stupid wizard of MS assumes that you are a part of a DOMAIN and expects to see the domain name as a part of your server name .

I wonder why they design wizards if one has to go eventually to scripts !!

will let you guys know if i have further updates!

Ali





Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

ali_khankan

Guys,

Do you have any more suggestions i am still stuck wih the Wizard.





Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

Janos Berke

Hi Ali,

I have had the same problem, but it solved Smile

I have a stand alone SQL Server 2005, without member of any domain. I put "local" to the "Primary DNS Suffix of this computer" textbox, then I specified my server as MyServer.local

Then it worked. Try this please. If it will not be working for you, then you have a problem of something else.

Regards,

Janos






Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

Narayan19

Janos,

where did you give this option and where did u specify this server as myserver.local. your reply will be appreciated.






Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

Janos Berke

Hi Narayan,

I tried to set up on my local machine with 3 instances this option. I got the same error message. I just got the idea to set up my computer to avoid this error like this:

  1. Right click on the "My Computer" then properties.
  2. Click on the "computer name" tab, then click on the change button next to the "To Rename this computer or join a domain, click change"
  3. then you see the "Computer name changes" window, click the "More" button on it.
  4. You will see the "DNS suffix and NetBIOS ComputerName" window. Here, type "local" to the "Primary DNS Suffix of this Computer" textbox.
  5. then press OK 3 times and restart computer.

After put this "computername.local" to your computer name for the mirroring computer server network address.

Regards,

Janos






Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

Narayan19

Thanks Janos, I will try it today and let you know for sure. again thanks for the reply.




Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

Narayan19

Janos,

I tried and it worked for me Thanks a lot for your detailed help i really appreciate it a lot.






Re: One or more of the server network addresses lacks a fully qualified domain name (FQDN).

Janos Berke

Hi Narayan,

I'm glad to hear it. If you are in domain environment, just use really the FQDN. This is applicable just in case of stand alone machine.

Regards,

Janos

Please mark the answer as helpful, when it was.